zabbix graph name marco

王艳玲

　　Traffic on interface {#SNMPVALUE} - {{HOST.HOST}:ifAlias[{#SNMPVALUE}].last()}
　　Zabbix has a default interface trigger which is raised when an interface status changes.
　　Good thing it would have been if we didn't have the same issue we had with the graphs; you don't have the interface description neither in the trigger's name nor in the comment. This is very annonying, especially if you receive alerts during the night.
　　Below an example of the default Zabbix trigger alert :

　　Seems like Ge1 operational status changed, good to know, but again what the hell is "ge1" ???
　　Message to Zabbix team : Do you really think I learnt all my switches port allocations by heart ???
　　The good news here is you can solve this stupidity with à "crafty" trick !
　　Trigger names/descriptions don't interpret items so using the "Zabbix Graph" trick [1] won't work...
　　To get your interface's description, you'll need to insert a "interface alias" item (ifAlias) in your trigger expression and reference it in the trigger name with the Zabbix standard macro "{ITEM.VALUEX}"
　　Go to "Configuration -> Templates -> Template SNMP Interfaces -> Discovery -> Trigger prototypes"
　　You should have a trigger named "Operational status was changed on {HOST.NAME} interface {#SNMPVALUE}" which matches the screenshot above.
　　To get the interface description, we first add a trigger expression that checks if the interface alias (i.e description) equals (str() function) a string that will NEVER match for example "this_does_not_exist" :
{Template SNMP Interfaces:ifAlias[{#SNMPVALUE}].str(this_does_not_exist)}=0　　This line means, the network interface description is NOT "this_does_not_exist" which is always true. Finally we add an AND operator (&) between the original expression and the string comparison which gives us the final trigger expression :
{Template SNMP Interfaces:ifOperStatus[{#SNMPVALUE}].diff(0)}=1&{Template SNMP Interfaces:ifAlias[{#SNMPVALUE}].str(this_does_not_exist)}=0　　This line means there were a interface operational status change AND the interface's alias is NOT "this_does_not_exist".
　　This alias comparaison is just a trick so we can reference the interface's alias (i.e description) with the "{ITEM.VALUEX}" standard macro.
　　Now change the trigger name with the following string :
  Operational status was changed on {HOST.NAME} interface {#SNMPVALUE} : {ITEM.VALUE2}　　As you can see, I added the macro {ITEM.VALUE2} that returns the name of the second item in the trigger's expression which is, you guessed it, the interface alias !
　　Wait until the discovery rule is refreshed (default is 3600s) or temporarily set it to 60s and enjoy the happiness of the result :

　　You can also use the {ITEM.VALUE2} macro in the trigger's description, very handy if you want to include additional information for the on-call guy.
　　In the next post [2], I'll show how to create a real interface trigger; from my point of view this default trigger is completely useless :

• 　　The trigger disappears after the next ifOperStatus check (60 seconds by default)
  
• 　　The trigger is raised when an equipment is plugged in. This is a "good to know information" but I can't rise a high severity trigger each time something is plugged !
  
• 　　I can't tell if the interface was up and went down OR if the interface was down and went up.
  
• 　　If I want to have a "Something was plugged in on GEX/X/X" trigger, I would make a special trigger for that purpose.