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

explore - loki log Histogram is not coming up, when we query for large interval #15017

Open
Uday599 opened this issue Nov 19, 2024 · 2 comments

Comments

@Uday599
Copy link

Uday599 commented Nov 19, 2024

We have grafana and loki deployed in EKS Cluster -

Histogram log are not coming up when we query for large interval ~more than 30mins. throwing gateway timedout.
would be helpfull if we know how this histogram is built

Error:
No logs volume available
No volume information available for the current queries and time range.

Grafana Version - grafana-8.4.8
Loki Version - loki-6.19.0

Please assist.

@mveitas
Copy link
Contributor

mveitas commented Nov 19, 2024

@Uday599 if you are using a reverse proxy such as nginx, make sure to check the configuration settings to allow for longer requests. We recently ran into this situation and had to set the annotation to configure the ingress configuration: nginx.ingress.kubernetes.io/proxy-read-timeout.

If you run the same sort of query that Grafana is doing via the CLI directly against Loki, you'll see that it most likely succeeds.

Grafana (browser) => kubernetes nginx ingress (this is where the error was) => Grafana => Loki

@Uday599
Copy link
Author

Uday599 commented Nov 19, 2024

Hi @mveitas , thank you very much for responding.

I have configured AWS load ingress load balancer,
grafana (browser) => ALB Ingress Controller => Grafana => Loki.

I tried increasing load balancer idle connection , still not able to see histogram,

error -
Failed to load log volume for this query

<title>504 Gateway Time-out</title>

504 Gateway Time-out

FYI- we were able to see log volume histogram when we query for like about 3hrs, 12hrs (though it takes time). but failing when we query for about 24hrs and more.

we were able to see complete logs, but histogram is not loading.
This query will process approximately 363.7 GiB for last 24hrs.

Would be helpfull, how actually this histogram is working in backend.

Please let me know if you need any info.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants