feat: avoid historical Loki live-tail queries#397
Merged
Conversation
thirdeyenick
reviewed
May 4, 2026
Contributor
thirdeyenick
left a comment
thirdeyenick
left a comment
There was a problem hiding this comment.
Looks good. So the QueryRange call query is more performant than the TailQuery call with longer periods of data, right?
Contributor
Author
|
Yes, exactly. |
thirdeyenick
approved these changes
May 4, 2026
Follow mode previously passed the normal log start time into Loki's websocket tail endpoint. With the default 30 day window, apps with a lot of logs could force Loki to establish a live tail over a big historical range, putting pressure on queriers and query frontends. We now fetch the requested backlog with the range query API first, then start the websocket tail from the end of that range.
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
2 participants
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.
Follow mode previously passed the normal log start time into Loki's websocket tail endpoint. With the default 30 day window, apps with a lot of logs could force Loki to establish a live tail over a big historical range, putting pressure on queriers and query frontends.
We now fetch the requested backlog with the range query API first, then start the websocket tail from the end of that range.