a description field for graphs
Moderators: Developers, Moderators
a description field for graphs
it would be usefull if each graph could have a description field that would come under the graph title where we could manually insert some furhter details, like for interface graphs, the CIR and EIR values of the interface we're graphing for example or any other info that would be usefull to have at a glance with the graph.
Insert a comment
just insert a comment in the graph template with the information the only problem is that comment are below the graph not above
I like this too. And best if this free defined field could be searchable. I have over 300 switches with over 3000 ports in cacti and if I am looking for switch X in the graph view, there is no real search function.
This field could have the customer contact info or name in there, so I can quickly find what switch a customer is on....
please..please...please
This field could have the customer contact info or name in there, so I can quickly find what switch a customer is on....
please..please...please
i like that!Anonymous wrote:I like this too. And best if this free defined field could be searchable. I have over 300 switches with over 3000 ports in cacti and if I am looking for switch X in the graph view, there is no real search function.
This field could have the customer contact info or name in there, so I can quickly find what switch a customer is on....
please..please...please
i second the motion of the honorable guest.
This would be a great feature, in fact the only one that is holding me up from switching 100% from MRTG.
We have a custom script that generates our MRTG graphs that lists the circuit ID, customer name, etc., so that its easily searchable. Since Cacti only allows for something similiar in the image, it kills the ability to search, which is important for our Ops people with a couple hundred graphs per host.
Having it also do query string replacement would be an added bonus vs. having to imbed it in the graph itself (i.e. auto-replacing things like |query_ifName| or |query_ifAlias|).
On all other fronts, Cacti has been a very valuable addition to our toolbox. Kudos to Ian and the rest of the contributors for their efforts.
-Doug
We have a custom script that generates our MRTG graphs that lists the circuit ID, customer name, etc., so that its easily searchable. Since Cacti only allows for something similiar in the image, it kills the ability to search, which is important for our Ops people with a couple hundred graphs per host.
Having it also do query string replacement would be an added bonus vs. having to imbed it in the graph itself (i.e. auto-replacing things like |query_ifName| or |query_ifAlias|).
On all other fronts, Cacti has been a very valuable addition to our toolbox. Kudos to Ian and the rest of the contributors for their efforts.
-Doug
Who is online
Users browsing this forum: No registered users and 1 guest