Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have a counter at stats.message.foo and want to move it to stats.messages.foo.

I've updated my code to populate the new counter, however the old one still exists.

I've read all I need to do to remove a stat from graphite is to delete the appropriate whisper file on disk, however it seems that within a few seconds of removing the wsp it gets regenerated (without data).

This is an annoyance if I want to rename the key that the data is stored under as I need to remember which key is the correct one.

Does anyone know how to permanently remove the old counter?

share|improve this question
    
If graphite keeps writing stats.message.foo its because something, somewhere is still sending that metric. I'd be looking at your statsd setup. –  Dave Wongillies Sep 3 '13 at 11:25
    
Did you ever find an answer for this? Suffering from the same problem. –  David Elner Sep 24 '13 at 15:34
    
@dave Unfortunately no. It's been a while and we've move to a new graphite server so the issue has "solved" itself. –  hafichuk Sep 25 '13 at 20:46

2 Answers 2

I had the same issue. I was able to remove the directory by first killing a StatsD server that was running. Perhaps this is the same issue you were having.

pkill statsd

share|improve this answer

I had a similar problem where entries still existed in Graphite although no data was available. I am using statsd and it didn't have metrics in there either. It turns out I had to delete these folders in addition to the wsp files.

My exact case is, I used the machine name as prefix for statsd. Carbon created folder for each of the machines in e.g /opt/graphite/storage/whisper/stats/ip-0A215A08, where it stored the wsp for my metrics. Because of that, once I deleted the wsp files, I still had a bunch of "folders" in Graphite w/o any data that still showed up in the UI.

Checks on Carbon/Graphite

  • .wsp files
  • directories for the stats you got rid of

On statsd (if you are using it), verify there are no more gauges, timers or counters for the metrics you want to get rid of. For this, you may also telnet on your instance (default port 8126) and check for metrics with proper commands of the Admin interface instead of killing the process.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.