Verify File Monitor source state and encoding#

When to use this procedure#

Use for File Monitor startup, read, conversion, and last-record events.

Applies to#

This procedure applies to EventReporter.

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 > File Monitor > affected service.

Procedure#

  1. Record source path, wildcard expansion, encoding, delimiter, and saved-position behavior.

    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.

  2. Run the native Windows checks below from the affected product host.

    Get-Item -LiteralPath '<SOURCE_FILE>' | Format-List FullName,Length,LastWriteTime,Attributes
$s=[IO.File]::Open('<SOURCE_FILE>','Open','Read','ReadWrite'); $s.Length; $s.Close()
Format-Hex -Path '<SOURCE_FILE>' -Count 32

    Expected result: The intended file is readable while the producer writes, and bytes match configured encoding/line endings.

    If it fails: Correct path, ACL/share mode, encoding, delimiter, or last-record delay before resetting position.

  3. 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.