Ad Widget

Collapse

Parse error messages from web scenario checks as a macro

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • y3046308
    Junior Member
    • Nov 2019
    • 1

    #1

    Parse error messages from web scenario checks as a macro

    Hi,

    I just setup dozens of web scenario checks in Zabbix.
    I also added triggers and one action for all the triggers.

    To test the action, i deployed a test bad web scenario check.


    However, an email message i got from the test only gave very high-level information:


    Problem: Service "Jira-QAS" is DOWN
    ------------​​​​​​​----​​​​​​​-------​​​​​​​----​​​​​​​----​​​​​​​----​​​​​​​-------​​​​​​​----​​​​​​​----​​​​​​​----​​​​​​​-------​​​​​​​----​​​​​​​----​​​​​​​----​​​​​​​----

    Application: CloudOps

    Problem started at 13:41:38 on 2019.11.20
    Problem name: Service "Jira-QAS" is DOWN
    Severity: High

    Status: PROBLEM
    Value: 1

    Original problem ID: 2314429
    ----​​​​​​​----​​​​​​​----​​​​​​​----​​​​​​​-------​​​​​​​----​​​​​​​----​​​​​​​----​​​​​​​-------​​​​​​​----​​​​​​​----​​​​​​​----​​​​​​​-------​​​​​​​----​​​​​​​----​​​​​​​----​​​​​​​----



    What I want is to parse "Last error message of scenario ..." as a macro and put it in the "default message" in "Action".


    So it would look something like this:


    Problem: Service "Jira-QAS" is DOWN
    ----​​​​​​​----​​​​​​​----​​​​​​​----​​​​​​​-------​​​​​​​----​​​​​​​----​​​​​​​----​​​​​​​-------​​​​​​​----​​​​​​​----​​​​​​​----​​​​​​​-------​​​​​​​----​​​​​​​----​​​​​​​----​​​​​​​----

    Application: CloudOps

    Problem started at 13:41:38 on 2019.11.20
    Problem name: Service "Jira-QAS" is DOWN
    Severity: High

    Issue: Couldn't connect to server: Failed connect to jira-qas.aws.ca:443; Connection refused

    Original problem ID: 2314429
    ----​​​​​​​----​​​​​​​----​​​​​​​----​​​​​​​-------​​​​​​​----​​​​​​​----​​​​​​​----​​​​​​​-------​​​​​​​----​​​​​​​----​​​​​​​----​​​​​​​-------​​​​​​​----​​​​​​​----​​​​​​​----​​​​​​​----


    I tried different macros such as {ITEM.VALUE}, {EVENT.STATUS} but neither of them were good enough.

    Can anyone share some insights?

    Thanks
Working...