Ad Widget

Collapse

Why can't I use {IPADDRESS} in trigger names???

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • frater
    Senior Member
    • Oct 2010
    • 340

    #1

    Why can't I use {IPADDRESS} in trigger names???

    I have a "Standalone" template added to several hosts I'm monitoring....
    {HOSTNAME} is filled with the name of the server which is behind a router....

    When I add this template I can only say, for instance, "{HOSTNAME} doesn't respond on ping", when in fact it's the router which is not responding on a ping.

    I wanted to use this syntax, but it didn't work

    Code:
    {HOST.CONN} doesn't respond on ping ({HOSTNAME})
    I can of course make a seperate HOST for the router connection, but this takes the beauty of using templates away...

    I understand why I can't use most of the variables as mentioned here in column 8, but I would really like {IPADDRESS},{HOST.CONN} and {DNS}

    http://www.zabbix.com/documentation/...pported_macros


    Could this be added to generate better readable messages?
    Last edited by frater; 28-07-2011, 18:50.
    Zabbix agents on Linux, FreeBSD, Windows, AVM-Fritz!box, DD-WRT and QNAP
  • eskytthe
    Senior Member
    Zabbix Certified Specialist
    • May 2011
    • 363

    #2
    Seems to be supported from 1.9.5 (alpha) ...
    http://www.zabbix.com/rn1.9.5.php
    ":: Support of new macros
    Added support for {IPADDRESS}, {HOST.DNS} and {HOST.CONN} macros in trigger names."
    BR
    Erik

    Comment

    Working...