You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am fond of the features Event > Search FROM timestamp and Search TO timestamp. They have a slight difference which I find annoying (in 2024.2.11282 at least):
Search FROM timestamp on event X finds events with timestamps >= X's timestamp.
Search TO timestamp on event Y finds events with timestamps < Y's timestamp.
If I'm wanting to review events from X to Y inclusive, a quick use of Search FROM and Search TO filters out event Y.
Workaround: Click on the time filter in the top right > add one millisecond to the TO timestamp.
It's a minor change, but it's pretty often I find myself using the workaround and thinking to myself I shouldn't have to do this.
Proposal:
Search TO timestamp on event Y finds events with timestamps <= Y's timestamp.
The text was updated successfully, but these errors were encountered:
Thanks for the suggestion @Jm-Fox 👍 The current behavior mirrors how ranges work in most programming languages, where the start bound is inclusive and the end bound is exclusive. That way, when you step through your data at range intervals you don't end up with overlapping results.
That's not necessarily helpful if you just want to see everything between two times though, so I think a Search TO Inclusive option would also be useful.
I am fond of the features Event >
Search FROM timestamp
andSearch TO timestamp
. They have a slight difference which I find annoying (in 2024.2.11282 at least):Search FROM timestamp on event X finds events with timestamps >= X's timestamp.
Search TO timestamp on event Y finds events with timestamps < Y's timestamp.
If I'm wanting to review events from X to Y inclusive, a quick use of Search FROM and Search TO filters out event Y.
Workaround: Click on the time filter in the top right > add one millisecond to the TO timestamp.
It's a minor change, but it's pretty often I find myself using the workaround and thinking to myself I shouldn't have to do this.
Proposal:
Search TO timestamp on event Y finds events with timestamps <= Y's timestamp.
The text was updated successfully, but these errors were encountered: