article Windows Event Log Scanner operation

The Windows Event Log Scanner works slightly differently from most other up.time monitors.  The principle difference is that it does not utilize a Recheck field.

 

In up.time versions up to 5.4, the monitor functioned by scanning the Event Log entries based on the value specified in the Number of Lines field.  When the monitor runs, it creates a temp check.  The next time it runs, it starts scanning the Event Logs from the temp check point going forward, up to the number of lines specified.  Only events generated since the last time the monitor was run will be detected, which ensures that events will alert only once and then have their status cleared on the next run.

 

In up.time 5.5, the WMI implementation was optimized by implementing a (non-configurable) 15-minute interval to scan Events instead of the Number of Lines variable.

Related Articles


Windows Event Log Monitor returns Output: Monitor failed: For inp...

RatingViews
article

This error indicates that the target agent server's up.time agent is incompatible with your monitoring station version. Please upgrade the agent on the impacted server and verify that this error is...

By: uptime Support | Date Created: 8-26-2010 | Last Modified: 8-10-2011 | Index: 497

  3154

Adding up.time port exceptions to Windows firewall

RatingViews
article

By: uptime Support | Date Created: 10-25-2005 | Last Modified: 7-13-2011 | Index: 024

  6749

Windows Executable Fails to Properly Initialize

RatingViews
article

By: uptime Support | Date Created: 9-10-2007 | Last Modified: 6-27-2011 | Index: 214

  2918

Installing the up.time agent on Windows

RatingViews
article

By: uptime Support | Date Created: 6-12-2006 | Last Modified: 7-25-2011 | Index: 079

  6773

Enabling Debugging in the Windows Agent

RatingViews
article

By: uptime Support | Date Created: 10-14-2005 | Last Modified: 7-6-2011 | Index: 010

  5545

User Comments



No comments have been posted.

Copyright © 2021 IDERA, Inc.   Legal   Privacy Statement