Graphite returning incorrect datapoint

Question

• I downloaded statsd and graphite 0.9.x
• I used the stats-client provided with source of statsd as follows:
  • ./statsd-client.sh \'development.com.

Answer 1

Have you tried using the stats_counts tree instead of stats? StatsD populates both for regular counters. stats by default does some fancy averaging which can tend make low-intensity stat signals disappear, whereas stats_counts just gives you the straight-up count, which sounds like what you want.

Answer 2

Within the whisper package, you will get a script- whisper-info.py. Invoke it on the appropriate metric file-

/whisper-info.py /opt/graphite/storage/whisper/alpha/beta/charlie.wsp

You will get something like this-

maxRetention: 31536000
xFilesFactor: 0.0
aggregationMethod: sum
fileSize: 1261468

Archive 0
retention: 31536000
secondsPerPoint: 300
points: 105120
size: 1261440
offset: 28

Here, make sure that aggregationMethod is sum, and xFilesFactor is 0.0. Most probably it is not, since this isn't graphite's default behavior. Now make a regex that picks up your metrics and put it at the beginning of the config file storage-aggregation.conf. This will ensure that the newly created metrics follow this new aggregation rule. You can read more about how xFilesFactor works here.