Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Migrate Winlogbeat to ECS, take 2 (#10333)
This pull request migrates Winlogbeat to ECS. Changed in this PR: - Nest most fields specific to Windows logs under "winlog.*" - Like we do for other log transports such as "syslog.*", "journald.*" etc. - Align multiple field names to the Windows Log naming (e.g. the Channel is no longer "log_name", but is "winlog.channel") - winlog.event_id is changing datatype from long to keyword - The process and thread ID of the event logging service are nested under "winlog." as a nesting of the ECS process field set, to make the experience consistent with ECS. - Fields migrated to ECS: - level => log.level (now lowercased) - xml => event.original - message_error => error.message - new ECS fields defined: - event.code is not yet in ECS, but may eventually be. It's a copy of winlog.event_id - event.kind - event.action - event.created - error.code Note that this PR only does a light adaptation to ECS, and does not look into event_data to parse out each source's information. This kind of processing is really source specific, and should be done server-side (e.g. Ingest Node). This way, improvements in event shaping can be done without a full re-deployment of Winlogbeat across a fleet of servers, and is also easier to customize for users.
- Loading branch information