Hi Hari, > -----Original Message----- > From: [EMAIL PROTECTED] On Behalf Of Hari Pulapaka > Sent: Tuesday, January 20, 2004 8:38 PM > > gmetric --name ypbind --value `pgrep ypbind` --type string > > And on the host with the gmetad, I can see the value for the above > metric, by doing: > > telnet localhost 8649 |grep ypbind > > What I want to know is, how do I see this in the grap that is > displayed > for the host (on the main web page) or in the Metric drop down box?
As far as I understood the webfrontend PHP code (talking about 2.5.5), it retrieves the metrics appearing in the drop-down boxes from a "first" host in an associative array of metrics within the PHP script. I'm not sure what defines this "first" host but I guess it could be based on the internal representation of the hash table or whatever is used there. In other words you can only be sure to see all metrics, if every cluster node spreads the same set of metrics. As a temporarily quick hack you might insert a debug statement in header.php where it says "Build the metric menu" like the following $firsthost = key($metrics); echo "firsthost=$firsthost"; exit; // this is added foreach ($metrics[$firsthost] as $m => $foo) Then request the webpage once and multicast the custom metric using gmetric on the cluster node which was printed by the debug statement. After that remove/uncomment the debug statement again. Besides that you can always specify the metric in the request URL even if it's not in the drop-down list. Be aware that the two last mentioned "solutions" might produce a lot of error logging because of inexistent rrd databases. To all: shouldn't those error messages be suppressed by the PHP code by checking for existence of rrd files before accessing them? HTH, Steffen.
