Cherry-pick #21205 to 7.x: [Winlogbeat] Add acceptable event log keys to winlog #21430
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
when running filebeat under elasti-agent 'id', 'meta' and 'revision' are sent as config keys to the winlog input type. This change allows those config keys to pass validation. (cherry picked from commit 499cc94)
|
Pinging @elastic/siem (Team:SIEM) |
botelastic
bot
added
needs_team
kaiyan-sheng
approved these changes
Sep 30, 2020
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 #21205 to 7.x branch. Original message:
What does this PR do?
Adds 'id', 'meta' and 'revision' as acceptable config keys for winlog
input.
Why is it important?
when running filebeat under elasti-agent 'id', 'meta' and 'revision'
are sent as config keys to the winlog input type. This change allows
those config keys to pass validation.
Checklist
- [ ] I have commented my code, particularly in hard-to-understand areas- [ ] I have made corresponding changes to the documentation- [ ] I have made corresponding change to the default configuration files- [ ] I have added an entry inCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.