Microsoft Windows
LyftData reads events from a Windows Event Log publisher channel with the windows-event-log input. Each event is emitted as JSON for the rest of the Job to process.
Prerequisites
Section titled “Prerequisites”- Run the Job on a Windows worker that can access the selected Event Log channel.
- Choose the publisher channel name and an Event Log query.
- A licensed LyftData edition. Windows Event Log is available in Licensed editions.
Read a Windows Event Log
Section titled “Read a Windows Event Log”Add windows-event-log to a Job and provide the required channel and query fields.
name: windows-security-eventsdescription: "Read events from the Windows Security channel"input: windows-event-log: channel: Security query: "*"output: file: path: "C:\\lyftdata\\events\\security.json"channel is the publisher channel to read. query filters the events. Leave start-at-oldest at its default, false, so the input keeps its saved bookmark and continues from the recorded position. Setting it to true discards the saved bookmark; in the current 3.0 releases it does not make the input read from the oldest record.
Failure behavior and troubleshooting
Section titled “Failure behavior and troubleshooting”channel and query are required. If the worker cannot open the channel or the query is invalid, the input cannot read events; verify the channel name, query syntax, worker permissions, and that the Job is running on Windows. The input keeps its bookmark in runtime artifacts so a resumed Job can continue from its recorded position.
Set debug-event-payloads: true only while investigating an event shape. The reference marks this as not recommended for production because it dumps expanded event log data. Leave it unset, or false, for normal operation.