Cherry-pick of PR #18966 to 7.x: Fix winlogbeat powershell event processing #18993
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cherry-pick of PR #18966 to 7.x branch. Original message:
What does this PR do?
Adds a function to dynamically calculate the number of chunks the dissect needs to parse for Powershell events.
It also improves the provided dashboard to show more information on the detail area.
Why is it important?
Powershell events carry a fixed amount of parameters. Seems to be that for downgraded events the number of parameters varies, so dissect failed for those.
Checklist
I have made corresponding changes to the documentationI have made corresponding change to the default configuration filesCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Screenshots
The updated dashboard