Verify Event Log channel access and bookmark state#
When to use this procedure#
Use for Event Log Monitor and Event Log Monitor V2.
Applies to#
This procedure applies to WinSyslog.
Prerequisites#
Use an account that can read the product configuration and Windows diagnostic state.
Replace angle-bracket placeholders with values from the affected system.
Safety#
Run diagnostic checks before changing configuration.
Remove passwords, private keys, license data, and other secrets from evidence.
Configuration path#
Configuration Client > Services > Event Log Monitor or Event Log Monitor V2 > affected service.
Procedure#
Record exact channel name, collection mode, service account, and intended start position.
Expected result: The affected object and its effective settings are identified.
If it fails: Return to the complete Event Log detail and configuration export before changing settings.
Run the native Windows checks below from the affected product host.
Get-WinEvent -ListLog '<CHANNEL_NAME>' | Format-List LogName,IsEnabled,RecordCount,LogMode Get-WinEvent -LogName '<CHANNEL_NAME>' -MaxEvents 5 | Format-List TimeCreated,Id,ProviderName,Message
Expected result: The channel is enabled and readable in the service-account context; a test event is collected once.
If it fails: Correct the channel name or least-privilege access; reset position only after recording replay impact.
Perform one uniquely identifiable product test through the same service, rule, or action.
Expected result: The intended destination records the test exactly once.
If it fails: Collect the first new product event and bounded debug output; do not change unrelated settings.
Verify the result#
Repeat the affected operation, confirm its positive output, and verify that queues, collection positions, or remote delivery continue normally.
Evidence to collect#
The complete Event Log entry and neighboring product events with timestamps.
The command output, relevant configuration export, and bounded debug log from the same interval.