Werk #1671: windows agent: fixed gaps in eventlog monitoring after agent restart

Component Checks & agents
Title windows agent: fixed gaps in eventlog monitoring after agent restart
Date Jan 20, 2015
Level Prominent Change
Class Bug Fix
Compatibility Compatible - no manual interaction needed
Checkmk versions & editions
1.2.7i1
Not yet released
Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)
1.2.7i1
Not yet released
Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)
1.2.7i1
Not yet released
Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)
1.2.7i1
Not yet released
Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)
1.2.7i1
Not yet released
Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)
1.2.7i1
Not yet released
Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)
1.2.7i1
Not yet released
Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)
1.2.7i1
Not yet released
Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)
1.2.7i1 Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)

The windows eventlog monitoring was not entirely continuous. After the agent started it determined determined the initial record number for each eventlog. Per default the start number was the last record. Thus resulted in monitoring gaps as long as the windows was not running, e.g. windows startup.

With this fix, the windows agent now uses a statefile (eventstate.txt) which contains the last processed eventrecord ids for each eventlog. On startup the statefile is read and the record numbers are set accordingly.

To the list of all Werks