Grafanano signalmediumCluster of 7 signals
Card #3615 · Grafana

Incorrect or missing interval variable calculation in queries

Users are experiencing issues where interval variables like __interval and __interval_ms do not reflect the expected time range or Min Step settings. This leads to incorrect data plotting, unexpected interpolation, or variables sticking to default values regardless of the selected time range.

GrafanaUpdated 1d ago0.18
Pain score
0.18/ 1.00 · weighted product of four components
Reach0.89
distinct authors (log-normalized)
Recency1.00
freshness decay, half-life months
Engagement0.56
upvotes + comments, normalized
Monetization0.25
willingness-to-pay cues in evidence
§ Evidence — 5 verified quotes
auto-complete shows __interval but not __interval_ms
Forum·@perconalab··source ↗
The __interval_ms should then return 60000, that is 60s, and not 200ms which is the value you see if you delete the Min Step size
Forum·@pparth··source ↗
I expect that the $__interval should be 1d or 24h, however it seems that it get the value of 30m
Forum·@fzhu1··source ↗
when the selected time range is less than 1 day, $count_interval gets the right value, but when it is more than 1 day, $count_interval just stick to 1d
Forum·@fzhu1··source ↗
Is there a way I can show just the actual points that exist in Prometheus and not interpolated points?
Forum·@dcadwallader··source ↗

Comments are a Pro feature — join the conversation, share what you've shipped, hear what others are building.

Upgrade to Pro