Skip to content
This repository has been archived by the owner on Nov 1, 2023. It is now read-only.

[Feature] Use winlogbeat processors to reduce unnecessary information in event logs #42

Closed
tfriesen opened this issue Nov 18, 2019 · 3 comments
Labels
enhancement New feature or request

Comments

@tfriesen
Copy link

With current defaults, winlogbeat logs a great deal of superfluous information, such as the PID and TID of the winlogbeat process.

This creates log entries that are full of useless information, which consumes storage space, slows down searching/indexing, and generally makes analyzing the data less pleasant.

Recommend using winlogbeat processors to cut down on some unnecessary fields. I've added the following data to the top of my winlogbeat.yml with good results:

processors:
  - drop_fields:
      fields: ["agent.ephemeral_id","agent.id","agent.type","agent.version","ecs.version","event.kind","winlog.api","winlog.opcode","winlog.process.pid","winlog.process.thread.id","winlog.provider_guid","winlog.record_id","winlog.user.domain","winlog.user.identifier","winlog.user.name","winlog.user.type","winlog.version"]
      ignore_missing: true

Granted, my approach is a little ham-fisted, and some of the data I've excluded others might want to include. NB that winlog.user.name, etc refers to the user the winlogbeat process is running as, NOT to the user that generated the event, and so is always NT AUTHORITY/SYSTEM.

@tfriesen tfriesen added the enhancement New feature or request label Nov 18, 2019
@tfriesen
Copy link
Author

There is also duplicate information, like event.code and winlog.event_id which always seem to be the same, and one or the other could be excluded (not done in my example)

@duncan-ncc
Copy link
Contributor

This sounds like a good idea and something we will look into in the future.

@duncan-ncc
Copy link
Contributor

Closed due to project archive

@duncan-ncc duncan-ncc closed this as not planned Won't fix, can't repro, duplicate, stale Apr 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants