Brad and all, Thanks a lot for clear explanation. But manual/automatic file editing doesn't directly fit well here. The basic problem is, as you said, 'chicken and eggs' type question. Gmond runs python metric module to generate metric descriptors list which forms the basis for metric definition file, but the metric definition file is referred by gmond again for XML reporting.
I've used gmetric in python script to workaround this type problem on haproxy status monitoring in AWS EC2 environment months ago. It was not an elegant solution but still worked well. That situation has been even more dynamic than multidisk -- as haproxy's proxyed services has been in change every few days, or even a few times a day some times; and every services' status array needs to be monitored and updated at any time. It will be perfect if some day new version ganglia metric module has a mechanism to solve dynamic metric (metric list generated from module) definition problem instead of falling back to gmetric. --Guolin -----Original Message----- From: Brad Nicholes [mailto:[email protected]] Sent: Tuesday, July 14, 2009 4:18 PM To: Guolin Cheng; [email protected] Subject: Re: [Ganglia-general] special metric names in diskusage.pyconf file >>> On 7/14/2009 at 4:36 PM, in message <4120cbd6bbd82647b89d6a70694510bed1c...@exchange02.presidio.alexa.com>, "Guolin Cheng" <[email protected]> wrote: > Hi, > > > > Any one knows what the metric name "<disk_used-metric-name>" stands > for? The stanza is from diskusage.pyconf file, ganglia version 3.1.1/2. > > > > collection_group { > > ... > > metric { > > name = "<disk_used-metric-name>" > > ... > > } > > ... > > > > It looks like that the name stands for a series of metrics output from > associated python module, but not sure what is the playing rule behind. > Any one can shed a light into this? Thanks a lot. > > It is a place holder for the actual metric name that isn't determined until you run gmond. Seems like a "chicken and egg" thing, but what you have to do is run gmond with the -m parameter first. This will give you a list of all of the possible metrics including those that come from diskusage.py. Then extract the actual diskusage metric names from the list and plug them into the .conf file. In most cases you will have to create additional metric blocks in the .conf file for each diskusage metric. Then start gmond normally and the individual disk usage metrics will be collected as expected. Brad ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ Ganglia-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ganglia-general
