When managing a lot of switchs, it's very difficult to remember that interface X of the switch Y is for the server of customer Z. Generally, you name the interface of the switch like the customer. So, putting the name of the interface in the name of the graph is a good idea.
If you manage a lot of switchs with a lot of interfaces, you probably love to use templates. But with templates, you can't customize the name of graphs...
So, here is the patch !
Just create a template with a graph named like this :
[22] Traffic ({:IF-MIB::ifAlias.22.last()})
In this example, it will display the value of item that monitors the description of the interface 22.
eg: [22] Traffic (my_customer)
You can see that it's the normal syntax of macros {server:key.function(param)} except that when you are on a template, there isn't hostname. So, if you don't put hostname, it will use the current hostname (of the graph displayed). If you put a hostname, it will just retrieves value for the item of that host.
It should be easy to use this code elsewhere (eg: triggers' name). I hope there isn't too much bugs...
This patch applies on Zabbix 1.4.5. The most of the code come from evalfunc.c, of zabbix-server.
If you manage a lot of switchs with a lot of interfaces, you probably love to use templates. But with templates, you can't customize the name of graphs...

So, here is the patch !
Just create a template with a graph named like this :
[22] Traffic ({:IF-MIB::ifAlias.22.last()})
In this example, it will display the value of item that monitors the description of the interface 22.
eg: [22] Traffic (my_customer)
You can see that it's the normal syntax of macros {server:key.function(param)} except that when you are on a template, there isn't hostname. So, if you don't put hostname, it will use the current hostname (of the graph displayed). If you put a hostname, it will just retrieves value for the item of that host.
It should be easy to use this code elsewhere (eg: triggers' name). I hope there isn't too much bugs...
This patch applies on Zabbix 1.4.5. The most of the code come from evalfunc.c, of zabbix-server.



Comment