Ad Widget

Collapse

Zabbix EventID trigger

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • drakeca
    Junior Member
    • Sep 2013
    • 5

    #1

    Zabbix EventID trigger

    Total newbie here, but I've been trying to get my way through this.

    I have a backup application which writes Information data to a log file on a Windows server. I want to send an email when a certain EventID is written to the log. So far I have created the following Item:

    eventlog[BACKUPSW,,,,6003,,]

    This works, and I can see data being logged if I check the Latest Data link for that server. I next tried to create a trigger and tried to save the following:

    {BACK-SRVR:eventlog[BACKUPSW].logeventid(6003)}=1

    The system won't allow me to save this and says the Key is incorrect. I tried to use the Expression Constructor and it came up with the following:

    {BACK-SRVR:eventlog[BACKUPSW,,,,6003,,].last(0,60)}=1

    This allows me to save the trigger, but when it collects the data I see an error message, with information "Format error or unsupported operator".

    Any suggestions on how I can get the trigger to kick in?

    Any feedback would be appreciated.
  • steveboyson
    Senior Member
    • Jul 2013
    • 582

    #2
    Try that one:

    {BACK-SRVR:eventlog[BACKUPSW,,,,6003,,]}.last(0,60)=1

    Comment

    • drakeca
      Junior Member
      • Sep 2013
      • 5

      #3
      Thanks for your quick response. I try to add the trigger, as you quoted, but receive the error message "Incorrect trigger expression. Check expression part starting from "{BACK-SRVR:eventlog[BACKUPSW,,,,6003,,]}.last(0,60)=1".

      It doesn't seem to like me moving the brace within the trigger statement.

      Comment

      • steveboyson
        Senior Member
        • Jul 2013
        • 582

        #4
        Hmmm you're right, the curly brackets are enclosing the last... statement.
        Sorry, my fault.

        Maybe something like

        {BACK-SRVR:eventlog[BACKUPSW,,,,6003,,].str("Some Error string:")}#0

        where "Some error string" is in your eventlog text could help.

        Comment

        • drakeca
          Junior Member
          • Sep 2013
          • 5

          #5
          Thanks mate, that seems to have fixed the problem!

          Comment

          Working...