Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Query timeout with larger offsets #12984

Open
jordanmat opened this issue May 17, 2024 · 0 comments
Open

Query timeout with larger offsets #12984

jordanmat opened this issue May 17, 2024 · 0 comments
Labels
component/querier type/bug Somehing is not working as expected

Comments

@jordanmat
Copy link

Describe the bug
When running query with count_over_time range [24h] , using offset higher than 48h my queries timeout.

To Reproduce

  1. Run query
sum by(container) (count_over_time({cluster="$Env", level="ERROR"} [24h] offset 72h))

this returns

Status: 504. Message: Get (http://...) context deadline exceeded (Client.Timeout exceeded while awaiting headers)

Expected behavior
The same query with an offsets up to 48h works fine, implying it's the amount of data that causes the timeout. Since my daily logs are roughly the same, querying each 24h period should not timeout. I assumed that using offset modifier will look at data from now() - offset and older, but seems like it's querying all the data?

Environment:

  • Infrastructure: Kubernetes
  • Loki: v2.9.4
  • Grafana: v10.0.0 (81d85ce802)
@JStickler JStickler added component/querier type/bug Somehing is not working as expected labels May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/querier type/bug Somehing is not working as expected
Projects
None yet
Development

No branches or pull requests

2 participants