Thanks Jay that was it. I had seen that string before but somehow it did not
click in my brain.
For those as slow as I am here is the fix. It really is too easy
I googled a RRD page and found that if I add -t in the graph custom definition
box that places anything that follows -t: as a Title of that graph.
For my issue I wanted to place the description entered in the Cisco router for
an interface. This is very useful for things like trunks of servers that really
do not move and once plugged into a switch port will stay there forever.
By using -t:${here/description} in the graph custom comments I now have a multi
graph of a switch and all the graphs are labled as to the device that port is
connected to.
Now when a graph spikes I can see immediately what it is connected to that is
causing the issue
Thanks again Jay for pointing me in the right direction.
-------------------- m2f --------------------
Read this topic online here:
http://forums.zenoss.com/viewtopic.php?p=38038#38038
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
