I have two non-linux systems that I have a specialized client on. On one of these systems, I have a special test for the CPU utilization of logical partitions. I used the NCV method of getting the data (LPARname:CPUvalue) into the RRD files supported by Hobbit. I have been able to add a graph to the status page for the LPAR column with a graph definition that lists each of the known LPARs in this system and the total value that is also sent. This has been working for several weeks. Now I am trying to add the second system. It has a different set of LPAR names. These LPAR names must be unique across our organization.

I asked our Hobbit admin to update the hobbitgraph.cfg with a modified [lpar] definition that included the second system's LPAR names in the hope that RRD would simply say that those entries from the other system were 'Not Available' or simply not display anything for them. I had hoped that I could use ONE graph definition for the [lpar] column no matter which system was supplying the data. Both graphs had an error about one of the OTHER's DS entries not being present. Is it possible to have two graph definitions for the same column, such as [vm1.lpar] and [vmhost.lpar] versus a single definition [lpar]?

Here are copies of the two status pages:

Thu Jan 18 10:05:06 EST 2007 General Processor LPAR utilization within thresholds LEGACY:1.0 ZOSEPROD:26.7 ZOSPROD:2.4 Total:30.1

Thu Jan 18 10:05:13 EST 2007 IFL Processor LPAR utilization within thresholds IFLPROD:1.3 Total:1.3

Here is the combined graph definition:

[lpar] TITLE z890 LPAR CPU Utilization YAXIS Percent FNPATTERN lpar.rrd -u 100 -l 0 DEF:LEGACY=lpar.rrd:LEGACY:AVERAGE DEF:IFLPROD=lpar.rrd:IFLPROD:AVERAGE DEF:ZOSPROD=lpar.rrd:ZOSPROD:AVERAGE DEF:IFLTEST=lpar.rrd:IFLTEST:AVERAGE DEF:ZOSEPROD=lpar.rrd:ZOSEPROD:AVERAGE DEF:Total=lpar.rrd:Total:AVERAGE LINE2:LEGACY#00cc00:Legacy LINE2:IFLPROD#00cc00:IFL-Production LINE2:ZOSPROD#ff0000:ZOSProd LINE2:IFLTEST#00cc00:IFL-Test LINE2:ZOSEPROD#0000ff:ZOSEProd LINE2:Total#ff00ff:Total COMMENT: \n GPRINT:LEGACY:LAST:LEGACY \: %5.1lf (cur) GPRINT:LEGACY:MAX: \: %5.1lf (max) GPRINT:LEGACY:MIN: \: %5.1lf (min) GPRINT:IFLPROD:AVERAGE: \: %5.1lf (avg) \n GPRINT:IFLPROD:LAST:LEGACY \: %5.1lf (cur) GPRINT:IFLPROD:MAX: \: %5.1lf (max) GPRINT:IFLPROD:MIN: \: %5.1lf (min) GPRINT:IFLPROD:AVERAGE: \: %5.1lf (avg) \n GPRINT:ZOSPROD:LAST:ZOSPROD \: %5.1lf (cur) GPRINT:ZOSPROD:MAX: \: %5.1lf (max) GPRINT:ZOSPROD:MIN: \: %5.1lf (min) GPRINT:ZOSPROD:AVERAGE: \: %5.1lf (avg) \n GPRINT:IFLTEST:LAST:LEGACY \: %5.1lf (cur) GPRINT:IFLTEST:MAX: \: %5.1lf (max) GPRINT:IFLTEST:MIN: \: %5.1lf (min) GPRINT:IFLTEST:AVERAGE: \: %5.1lf (avg) \n GPRINT:ZOSEPROD:LAST:ZOSEPROD \: %5.1lf (cur) GPRINT:ZOSEPROD:MAX: \: %5.1lf (max) GPRINT:ZOSEPROD:MIN: \: %5.1lf (min) GPRINT:ZOSEPROD:AVERAGE: \: %5.1lf (avg) \n GPRINT:Total:LAST:Total \: %5.1lf (cur) GPRINT:Total:MAX: \: %5.1lf (max) GPRINT:Total:MIN: \: %5.1lf (min) GPRINT:Total:AVERAGE: \: %5.1lf (avg) \n

/Thomas Kern /301-903-2211