Ad Widget

Collapse

Windows event log - not always triggering

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • HullZabbix
    Senior Member
    • Feb 2011
    • 104

    #1

    Windows event log - not always triggering

    I seem to be having a problem with zabbix monitoring windows event logs. My trigger won't always trip

    Item:
    eventlog[Application]

    Trigger:

    {Template1Servers:eventlog[Application].logseverity(0)}=4 & {Template1Servers:eventlog[Application].logeventid(1107|1106|1116)}#1 & {Template1Servers:eventlog[Application].nodata(2)}#1

    So in theory this should be picking up all "errors" excluding event id's 1107,1106 and 1116.

    I've set the .nodata(x) to 1,2,3,4 in turn. I still get the issue.

    I want this trigger to clear as soon as an email is sent via an action I've set up.

    Action Conditions:
    A and B
    Trigger = "Template1Servers:Eventlog: All Application Errors"
    Trigger value = "PROBLEM"

    Checking the "latest data" the events are actually there. They just don't get picked up by the trigger sometimes.

    It seems very random when logs will trip the trigger.

    Anyone have any suggestions? I've run out of ideas

    *edit*
    It's got a lot worse since upgrading from 1.8.1 to 1.8.5
    Last edited by HullZabbix; 13-05-2011, 15:15.
Working...