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 'min step' of 1m loses fine detail #339

Closed
bboreham opened this issue Jun 25, 2021 · 0 comments · Fixed by #340
Closed

Query 'min step' of 1m loses fine detail #339

bboreham opened this issue Jun 25, 2021 · 0 comments · Fixed by #340

Comments

@bboreham
Copy link
Contributor

I find this setting problemmatic:

It is shown in the Grafana UI as 'min step'.

Here it is documented that $__rate_interval will be floored at 4x this quantity, i.e. 4 minutes. This makes it impossible to see fast transients in the data.

Further, Cortex query-frontend will quantise start and end times to a multiple of the step time, so dashboards only change every minute.

Since we are scraping at 15s I propose "min step" should be 15s.

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

Successfully merging a pull request may close this issue.

1 participant