Ad Widget

Collapse

Reason to mention {HOST.NAME} in trigger?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • nobodysu
    Member
    • Sep 2016
    • 84

    #1

    Reason to mention {HOST.NAME} in trigger?

    Why it's a general rule to mention {HOST.NAME} in trigger's name? Anywhere I can see a trigger - I can see hostname also.
    Is this macro really necessary?
  • kaspars.mednis
    Senior Member
    Zabbix Certified Trainer
    Zabbix Certified SpecialistZabbix Certified Professional
    • Oct 2017
    • 349

    #2
    Hello

    one of the reasons i use this - you may use then the {TRIGGER.NAME} macro in actions and forward complete info with one macro to sms/email etc...

    regards,
    Kaspars

    Comment

    • nobodysu
      Member
      • Sep 2016
      • 84

      #3
      For actions then. OK, thank you for the information!

      Comment

      • kloczek
        Senior Member
        • Jun 2006
        • 1771

        #4
        Originally posted by nobodysu
        Why it's a general rule to mention {HOST.NAME} in trigger's name? Anywhere I can see a trigger - I can see hostname also.
        Is this macro really necessary?
        To be honest there is nos such reason.
        Why? Because:
        - in view of active triggers in the same line is present host name on which trigger is active and repeating this name makes active triggers view only less readable.
        - when trigger is used for example on constructing email body or subject trigger massage and host name are available as macros.
        http://uk.linkedin.com/pub/tomasz-k%...zko/6/940/430/
        https://kloczek.wordpress.com/
        zapish - Zabbix API SHell binding https://github.com/kloczek/zapish
        My zabbix templates https://github.com/kloczek/zabbix-templates

        Comment

        Working...