Today, Steven A. DuChene wrote forth saying... > I want to add some additional info to the ganglia data stream. Things > like system serial numbers and other values that will not change over a > period of time. > > I see gmetric has a -d option for "The lifetime in seconds of this > metric" so I would assume for something like system serial number I > would set that pretty high.
actually.. you would set it very low: zero. zero is special and means to never delete the metric. of course, you can change this value when you send the metric at a later time if you want to delete it. > Can anyone provide some additional explanation or detail for the -x (The > maximum time in seconds between gmetric calls) and the -s (slope) > options? Does the -x option determine how long between refreshes of this > metric and thus I should put the call to this metric fron the cron > system at a time interval less than this? Or am I misunderstanding what > this option does exactly? As to the -s slope option an example of > why/when this might be used would be most helpful as I don't see any > additional info on this option so I am not understanding how it would be > used. the -x option is used to inform clients that are polling your data just how fresh the data is. this is the TMAX value in the XML output. clients understand that if TN (time now) is > TMAX then we do not have fresh data (either a message was missed or the data source is no longer transmitting the metric). the -s option is important to gmetad. if -s is set to "zero" then gmetad does not waste time storing historical values for the metric (since the value is a constant). btw, gmetad also ignores non-numeric values. right now all non-zero slopes are stored as rrdtool gauges...in future the positive and negative only metrics will be stored as an rrdtool counter. make sense? let us know if you have any more questions -matt
