On Fri, Aug 25, 2006 at 12:56:41PM -0500, Hubbard, Greg L wrote:
Yep, the problem is really in how the RRD is set up. I have some custom scripts that simply "wc -l" some files and these go into an RRD as a gauge...I thought this function might let me get out from under all the custom moving parts, but no luck in this release.
I figured that out from your previous mail - that you've been using a GAUGE RRD file, whereas the linecount function uses a DERIVE file.
In fact, since the GAUGE/DERIVE setting is only used when the RRD file is created, you could - as a workaround - create the RRD file by hand, and then just use the current linecount function to update it. That would work, I think.
But I also use "DERIVED" counts to see what my incoming syslog and trap rates are -- so the linecount function could replace these custom scripts, except that the way I have it now these items get their own status dot and a nicely labeled graph. The new linecount graphs are buried in the "trends" stack so you have to know to go look for them there.
Several nice ideas here; the ability to track absolute linecounts is reasonable, and having a way of configuring what graphs go on what status columns has been discussed before - it is definitely one of those things that really need improvement. And I think it would be a good idea to create status columns from any RRD data item that we have, which would solve your last point.
Lest I sound too much like a whiner -- I really like where Henrik is taking us all with each new Hobbit release!
Thanks, but it's a long journey. Each time we get a little closer, though.
Regards, Henrik