Value-Stat=current shows different values when choosing different timeranges

Hi all,

Im using graphite (0.9.16) with grafana (4.5.2) and build a dashboard showing some Singlestats.
One row I configured with Value-Stat=current and the other row I configured with Value-Stat=avg.

I assumed, that the values displayed for the Singestats with stat=current stay the same nevertheless which timeranges I pick. Since current means “last” value. But when I switch from “last 5 minutes” to “last 2 days” the values changed. Between “last 5 minutes” and “last 1 hour” the values are the same.

Is that a bug? Or configuration error?

my graphite storage-schemas:
pattern = ^carbon.
retentions = 60:90d

pattern = ^icinga2\..*\.(max_check_attempts|reachable|current_attempt|execution_time|latency|state|state_type|acknowledgement|downtime_depth)
retentions = 5m:60d

pattern = ^icinga2\..*\.services\.icinga\.
retentions = 1m:7d,5m:30d

pattern = ^icinga2\.
retentions = 1m:60d,5m:180d,10m:5y

pattern = .*
retentions = 60s:1d

the icinga_default should apply here.

Okay I found out that it has something to do with the “Max data points” which are returned by graphite. The default is 100 but when I change with timepicker to “last two days” then graphite returns values for every 14 minutes with some kind of average I think.
When I change the max datapoints to 1000000, the value stays current even with “last two days”

Can anybody explain that to me? :wink: