-
Notifications
You must be signed in to change notification settings - Fork 355
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
[bug] default resolution is too low #50
Comments
The default resolution of 30s is too low for some Prometheus metrics servers and will result in no data returned for the query. An increase to 1m should fix the issue. Fixes dotdc#50
I added the resolution variable in an attempt to see spikes in a very specific case. In case anyone needs it, it's pretty easy to edit a panel to add it back. |
@dotdc In general, I would agree. Though I've seen the rate internal variable also not work and I don't think it's configurable by the user? |
The What is your Scrape Interval? If it's the case, maybe the issue is tied to Grafana Mimir and/or your configuration. Maybe it's worth opening an issue there too. I'll keep the PR as is for now, but I would rather delete the |
Hmm, Grafana agent is configured with a 15s scrape interval. Though, changing the value to |
Interesting... |
Signed-off-by: David Calvert <david@0xdc.me>
If anyone has further knowledge on this issue, feel free to open a PR to update the documentation. |
Describe the bug
The default resolution of 30s is too low and renders some dashboards with "No Data". This is likely because I'm using Grafana Mimir, as opposed to a standard Prometheus install.
How to reproduce?
Expected behavior
Changing the resolution from 30s to 1m shows the data as expected.
Additional context
No response
The text was updated successfully, but these errors were encountered: