在使用StatsD和Graphite时,我在不同的时间范围内查看相同的stats_counts.*
指标值时遇到了问题:
从上图中可以看出,当选择更大的时间范围时,相同的测量数据会被视为不同。
我会理解由于Whisper在旧数据上使用的存储聚合方案而导致的准确度不高,但这并不能解释最近的数据是如何显示的,因为它在不同的时间范围内具有不同的值。 / p>
仅供记录,我的schema_aggregation.conf
看起来像这样:
[munin]
pattern = ^munin\..*
xFilesFactor = 0
aggregationMethod = average
[min]
pattern = \.lower$
xFilesFactor = 0.1
aggregationMethod = min
[max]
pattern = \.upper$
xFilesFactor = 0.1
aggregationMethod = max
[sum]
pattern = \.sum$
xFilesFactor = 0
aggregationMethod = sum
[count]
pattern = \.count$
xFilesFactor = 0
aggregationMethod = sum
[count_legacy]
pattern = ^stats_counts.*
xFilesFactor = 0
aggregationMethod = sum
[logster]
pattern = ^logster\..*
xFilesFactor = 0
aggregationMethod = sum
[default_average]
pattern = .*
xFilesFactor = 0.3
aggregationMethod = average
和我的storage-schemas.conf
:
[carbon]
pattern = ^carbon\..*
retentions = 60:90d
[munin]
pattern = ^munin\..*
retentions = 10s:6h,1min:7d,10min:5y
[stats]
pattern = ^stats\..*
retentions = 10s:6h,1min:7d,10min:1y
[stats_counts]
pattern = ^stats_counts\..*
retentions = 10s:6h,1min:7d,10min:1y
[logster]
pattern = ^logster\..*
retentions = 60s:12h,10m:1y
# [default_1min_for_1day]
# pattern = .*
# retentions = 60s:1d
知道可能出错的是什么?也许是我错过的配置?
答案 0 :(得分:2)
看起来你正在遇到常规的Graphite行为,当你有更多的x轴数据点而不是图中的像素时,它会平均y值(因为2h的数据有720个数据点)。当您使用&width=1000
查看图表时,是否也会发生这种情况?