Allen is correct, I no longer distribute those reports that you listed. Bear in mind that the Organized Graphs are merely examples for you to build your own reports using the template that I created.
That being said, you should be able to easily remedy the errors using the "sister" report examples, as follows: 1. delete Custom_ControlBlock_Layout completely, I replaced this with Custom_Graphs and will not bother to fix the older one up 2. Memory is a perf graph, like Load, so copy the Load_Graphs.rpt as Memory_Graphs.rpt, replace the line that reads: gtype string:Load; with this: gtype string:Memory; and reload all files using ReportLoader.py. This can also be done with any other performance tabs in the Zenoss system. 3. Likewise, SubLocations/SubGroups are pretty much identical to SubSystems. Similar to #2 above, just merely clone SubSystems_Graphs.rpt as SubLocations_Graphs.rpt and change: otype string:Systems; to this: otype string:Locations; which will work for Groups as well... As you can see, it was redundant to maintain more than one type of perf/intf/org graph, so I cut it down to one each. In case anybody doesn't realize, gtype=GraphType and otype=OrganizerType. Hope that helps. The legacy reports probably won't need to be changed again anytime soon because I have no more additional features that I can think of adding after 1.4-5. Now that graph filtering and labeling are done, next things on my agenda was to to figure how to reuse my graphAggregate plugin to create graph "clusters" as then try yo do some custom RRD insertion and subsequent report extraction. -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=6095#6095 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
