Ad Widget

Collapse

Host defined macro in trigger and graph names

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • spincon
    Junior Member
    • Nov 2010
    • 3

    #1

    Host defined macro in trigger and graph names

    Hello,

    i am exploring the use of macro in my templates but i am facing an issue, the host defined macro are not replaced in trigger names and graph names ??

    Is it the way it should work or is there someting i am doing bad ?

    Thanks in advance,
    Stephane
  • alixen
    Senior Member
    • Apr 2006
    • 474

    #2
    Hi,

    According to documentation (http://www.zabbix.com/documentation/.../config/macros), host level macros {$MACRO} are supported in trigger names but not map labels.

    Regards,
    Alixen
    http://www.alixen.fr/zabbix.html

    Comment

    • spincon
      Junior Member
      • Nov 2010
      • 3

      #3
      Thanks for your reply,

      did you succeed in setting a trigger name with a host defined macro ?

      When i receive an alert email, the topic is
      MGAIABDDDEV - Oracle - {$SID2} - Deadlock detected: PROBLEM
      but {$SID2} is set in the host parameters... So i do not understand...

      Stephane

      Comment

      • alixen
        Senior Member
        • Apr 2006
        • 474

        #4
        Hi,

        Originally posted by spincon
        did you succeed in setting a trigger name with a host defined macro ?

        When i receive an alert email, the topic is
        MGAIABDDDEV - Oracle - {$SID2} - Deadlock detected: PROBLEM
        but {$SID2} is set in the host parameters... So i do not understand...
        Just checked in 1.8.3:
        I have modified my ping trigger description:
        Code:
        Ping failed on {HOSTNAME} (Timeout : {$ICMPPING_TIMEOUT})
        ({$ICMPPING_TIMEOUT} is defined in my 'icmpping' template)

        In Monitoring->Events and Monitoring->Triggers I see:
        Code:
        Ping failed on myserver (Timeout : {$ICMPPING_TIMEOUT})
        Obviously, {HOSTNAME} is replaced but {$ICMPPING_TIMEOUT} is not.

        So there is a bug either in Zabbix code or documentation.

        Time to open a bug report ?

        Regards,
        Alixen
        http://www.alixen.fr/zabbix.html

        Comment

        • spincon
          Junior Member
          • Nov 2010
          • 3

          #5
          Thanks for your reply,

          i've checked on zabbix site and this issue should be resolved in 1.8.4...

          Stephane

          Comment

          Working...