You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using prometheus 2.16.0 and grafana 6.6.2
There is a job with scrape_interval = 500ms.
Tried everything to get precise data with 0.5sec resolution - nothing works.
The main goal is to get graphs on Grafana, but it seems not to pass the resolution down to prometheus.
Instant queries using Grafana - returns data, but only the last datapoint not a time range Only queries to Prometheus Api - returns right data, but with some duplicates (aggregation as i see)
We played around with this and confirmed that the API is actually capable of serving step sizes below 1s. You can specify a step like 100ms or plainly 0.1. However, the UI will never request this resolution even if you ask for it in the form field. So that latter point is valid and should be improved.
Using prometheus 2.16.0 and grafana 6.6.2
There is a job with scrape_interval = 500ms.
Tried everything to get precise data with 0.5sec resolution - nothing works.
The main goal is to get graphs on Grafana, but it seems not to pass the resolution down to prometheus.
Instant queries using Grafana - returns data, but only the last datapoint not a time range
Only queries to Prometheus Api - returns right data, but with some duplicates (aggregation as i see)
curl -s 'http://localhost:9090/api/v1/query_range?query=metric_name&start=1582643556&end=1582643756&&step=200ms' | jq
Scrape interval for datasource in grafana, min step, min time interval are all set.
Even prometheus global scrape interval is set to 500ms.
Setting resolution in graph console doesn't make any change - it parses values like seconds as seen on the right side:
So even if you set 0.5 or 0.5s it parses it like 1s...
What can be wrong?
The text was updated successfully, but these errors were encountered: