This is useful when gmetad is configured to send data to graphite.
Instead of writing out rrds natively and then whisper files later,
just send the data to carbon and let it write out whisper files.
NOTE: I'm still relatively new to doing much with C other than reading it.
This is a RFC, not a Please merge this I think I am awesome. I'm curious if this is the right approach to disable writing of rrds by gmetad. In our instance, I'd like to put gmetad and the main carbon instance on the same webserver, but I'd rather have ganglia-web pull the graphs from graphite directly. A double IO hit from carbon/whisper + rrdtool slamming the disk is suboptimal.
Is this approach even close to what you'd consider merge worthy?
Add 'write_rrds' option for disabling rrds
I tested a few incarnations of with/without rrds already created and gmetad -d 100. It didn't write out any rrds when I put write_rrds off in the config. If this approach is ok, I'll add a commented out example to the gmetad config file.
gmetad -d 100
I think this would be a useful option.
I was working on a gmetad-python.py version of this option by simply not installing the rrd plugins.
The goal was to have the ability to use gmonds to gather metrics and offload the overhead of disk IO etc if I wanted to other nodes. I abandoned that work now that 3.3.X can forward metrics, but having the option to turn off rrd creation would be good.