Ad Widget

Collapse

{EVENT.ID} Macro not working

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • bagendron
    Junior Member
    • Jul 2016
    • 5

    #1

    {EVENT.ID} Macro not working

    I'm trying to use the {EVENT.ID} macro so we can tie the OK to the Problem. However, the results in the log file shows different values for the Problem and associated OK. We are running Zabbix 3.0.

    Here is the action body of the failing Alert followed by the result written to the log...
    "{EVENT.DATE} {EVENT.TIME} Host:{HOST.NAME},Trigger:{TRIGGER.NAME},Trigger status: {TRIGGER.STATUS},Trigger severity: {TRIGGER.SEVERITY},event ID: {EVENT.ID}"

    1473185461 Host:XXXX,Trigger:Timestamp changed,Trigger status: PROBLEM,Trigger severity: Critical,event ID: 7243421
    1473185464 Host:XXXX,Trigger:Timestamp changed,Trigger status: OK,Trigger severity: Critical,event ID: 7243422

    I've tried this with recovery message checked and unchecked

    Also, we send critical alerts using a separate rule to a slack channel and the ID sent to slack using the same macro works as expected.

    Thank you for the help
    Bob
  • peatb
    Zabbix Certified Trainer
    Zabbix Certified Trainer
    Zabbix Certified SpecialistZabbix Certified Professional
    • Aug 2016
    • 36

    #2
    An event in this case is the fact that the trigger changes its state.
    So the trigger going to PROBLEM is an event, the trigger going to OK is a new event. That's why the id's are different.

    Comment

    • bagendron
      Junior Member
      • Jul 2016
      • 5

      #3
      Thanks for the reply,

      Your answer made me realize the Trigger value = PROBLEM was missing from the conditions. Once I put that into the rule it began to work as expected. The problem and ok messages both contain the original event id now.

      Bob

      Comment

      Working...