feat: LQL timestamp support for unix timestamps and ISO8601#3327
Draft
msmithstubbs wants to merge 1 commit intoLogflare:mainfrom
Draft
feat: LQL timestamp support for unix timestamps and ISO8601#3327msmithstubbs wants to merge 1 commit intoLogflare:mainfrom
msmithstubbs wants to merge 1 commit intoLogflare:mainfrom
Conversation
4810ec7 to
7355e59
Compare
7355e59 to
6a3d953
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add support for LQL timestamp filters in these formats:
Unix timestamp
Use Unix timestamps as 10-digit seconds, 13-digit milliseconds, or 16-digit microseconds.
Microsecond values are truncated to milliseconds.
Unix timestamps are interpreted as UTC.
Examples:
t:>=1710683222000t:<=1710683222000000t:1710683222..1710683822t:1710683222000..1710683822000ISO8601 format
A timestamp can be written as:
This is interpreted in the user’s selected timezone.
This is treated as a UTC datetime.
This is treated using the supplied offset.
Examples:
t:2026-03-17..2026-03-19t:>2026-03-17T14:47:02Zt:>=2026-03-17T14:47:02.123Zt:<2026-03-17T14:47:02+02:00t:>=2026-03-17T14:47:02-02:00t:2026-03-17T14:47:02+02:00..2026-03-17T15:47:02+02:00