Poking through Ganglia, and some of the metrics it gathers, I think it might
need to support a "unit number" or similar attribute for the metrics.
For example, there's only one 'cpu_speed' metric. Sparc (and at least some)
x86 motherboards let you have different processors running at different
speeds. . .
For example, a dual processor system would have:
<metric name="cpu_speed" unitnum="0" val="750" ...>
<metric name="cpu_speed" unitnum="1" val="750" ...>
Of course, then I look at this and start thinking that what might be even
nicer (if less newbie friendly) would be to use SNMP OIDs as the value of
the name attributes, since the OIDs tend to encode things like unit number,
units, and other pieces of information. Then you'd have a lot of
<metric name="1.2.3.4.5.6.7.8.9.0" val="foo">
<metric name="0.9.8.7.6.5.4.3.2.1" val="bar">
instead. It would then be the job of the graphing/reporting application to
map OIDs back to useful names.
Hmm.
In other news, I hope ($employer willing) to be able to release a version of
solaris.c that gathers the same metrics as freebsd.c and linux.c, without
needing to resort to running shell scripts that run gmetric. More news when
I hear back from the lawyers.
N
--
1234567890123456789012345678901234567890123456789012345678901234567890123456
7890
-- The 80 column-ometer
Global Messaging Victoria Plaza, 2nd Floor x21206
