New question #201519 on Graphite: https://answers.launchpad.net/graphite/+question/201519
Hi! I recently started using collectd to shove metrics in graphite. It worked well on small scale for a few days, but when I rolled it out everywhere, I began noticing that data were getting "lost". All my other data/whisper files are fine. But when I look at collectd data, I only see the latest datapoint. I'm using http://github.com/indygreg/collectd-carbon.git to get data to graphite.. and at one point, I had changed the collectd interval from 10s to 60s -- I thought "hmm, perhaps like RRD, I'll have to start over" ... I deleted the whisper files for collectd, and sure enough I started seeing data. But the next day, this is my data: drawAsInfinite(stats.prod.ops.collectd.apiservices-a012.memory.buffered),1338139200,1340731200,600|None,None,None,None,None,.... followed by ~1000 "None" items. The mtime on the files are all recent - around 1 minute. Therefore collectd is sending, and I don't have any relay-rules or other craziness causing this - data is getting there... but only one data point is kept :( Anyone experienced this? Or have ideas for debugging steps? Thanks :) -Charlie -- You received this question notification because you are a member of graphite-dev, which is an answer contact for Graphite. _______________________________________________ Mailing list: https://launchpad.net/~graphite-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~graphite-dev More help : https://help.launchpad.net/ListHelp
