Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Winlogbeat] Document 21 Event ID clause limit under certain situations #35049

Merged
merged 2 commits into from Apr 10, 2023
Merged

[Winlogbeat] Document 21 Event ID clause limit under certain situations #35049

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
dc7afce
[Winlogbeat] Document 21 Event ID clause limit under certain situations
taylor-swanson Apr 10, 2023
3b4bfc8
Update changelog
taylor-swanson Apr 10, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
1 change: 1 addition & 0 deletions CHANGELOG.next.asciidoc
View file
Open in desktop
Expand Up @@ -301,6 +301,7 @@ automatic splitting at root level, if root level element is an array. {pull}3415

- Add metrics for log event processing. {pull}33922[33922]
- Add metrics documentation for event processing. {issue}34887[34887] {pull}34889[34889]
- Add note in documentation about 21 event ID clause limit {issue}35048[35048] {pull}35049[35049]

*Elastic Log Driver*

Expand Down
6 changes: 5 additions & 1 deletion winlogbeat/docs/winlogbeat-options.asciidoc
View file
Open in desktop
Expand Up @@ -251,7 +251,11 @@ logs.
`WARN EventLog[Application] Open() error. No events will be read from this
source. The specified query is invalid.`

If you have more than 22 event IDs, you can workaround this Windows limitation
In some cases, the limit may be lower than 22 conditions. For instance, using a
mixture of ranges and single event IDs, along with an additional parameter such
as `ignore older`, results in a limit of 21 conditions.

If you have more than 22 conditions, you can workaround this Windows limitation
by using a drop_event[drop-event] processor to do the filtering after
{beatname_uc} has received the events from Windows. The filter shown below is
equivalent to `event_id: 903, 1024, 4624` but can be expanded beyond 22
Expand Down