Ad Widget

Collapse

Actions - trigger - zabbix 3.2

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • mislav-eu
    Member
    • May 2016
    • 30

    #1

    Actions - trigger - zabbix 3.2

    Hi there.

    In old zabbix I have under actions - conditions option Trigger value - I'm just reading documentation for 3.2 and my instance of 3.2 - there is no trigger value in conditions (apparently removed according to the upgrade notes).

    Is there a replacement for it? How to "get" now triggers with value PROBLEM ?
    Last edited by mislav-eu; 17-11-2016, 16:55.
  • mislav-eu
    Member
    • May 2016
    • 30

    #2
    BUMP!

    Also, is documentation on the latest version?

    e.g.


    and other documentation - trigger.status is removed in 3.2, why is it still there? If I try to use it in custom script - script is not even executed.

    Next, not even {TRIGGER.NAME} is working in Actions as macro - script is not executed and there is no error display.

    Am I doing something wrong or 3.2 is not working still properly? I'm using zabbix 3.2.1.

    Comment

    • Atsushi
      Senior Member
      • Aug 2013
      • 2028

      #3
      It is not necessary to specify the Trigger value in the condition of the action.

      If it is PROBLEM, processing on the Operations tab is executed.
      If it is OK, processing on the Recovery operations tab is executed.

      If you want to send only the recovery message after PROBLEM,
      try selecting "Send recovery message" as the Operation type on the Recovery operations tab.

      There is no change to the macro {TRIGGER.STATUS} available within the action.

      Comment

      • mislav-eu
        Member
        • May 2016
        • 30

        #4
        Unfortunately, it's not working, at all.

        Not even trigger.name as mentioned, in the actions. I've made simple sh script which just echo-es $1 $2 parameters in file and only zabbix admin emails are echo-ed there and hostname of the server - if I add anything else, it doesn't work and script is not executed.

        I've even tried switching debug log level to 4 and there was nothing in it.

        Comment

        • Atsushi
          Senior Member
          • Aug 2013
          • 2028

          #5
          Did you set arguments when creating a simple script?

          {ALERT.SENDTO}
          {ALERT.SUBJECT}
          {ALERT.MESSAGE}


          If the script is not executed, check the access permission to the failed host.

          Comment

          • mislav-eu
            Member
            • May 2016
            • 30

            #6
            I've those parameters and they're only working if I type e.g. "test subject" into subject field and "some message" in message field.

            If I try to use macro there - it doesn't work. On the other hand if I use hostname macro in any of those two fields - it works.

            Comment

            Working...