Cherry-pick #23273 to 7.11: Reorder headers for infoblox module #23302
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
* Reorder headers for infoblox module This reorders the syslog headers parsers for the infoblox/nios dataset so that the simpler header is picked up first. Otherwise it will fail to properly parse logs. Fixes elastic#23272 * Changelog entry (cherry picked from commit 27d0f08)
botelastic
bot
added
the
needs_team
|
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
botelastic
bot
removed
the
needs_team
andrewstucki
approved these changes
Dec 28, 2020
💔 Build Failed
Expand to view the summary
Build stats
Steps errors
Expand to view the steps failures
|
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 #23273 to 7.11 branch. Original message:
What does this PR do?
This reorders the syslog headers parsers for the infoblox/nios dataset so that the simpler header is picked up first.
Why is it important?
Otherwise it will fail to parse logs in the default configuration.
Checklist
[ ] My code follows the style guidelines of this project[ ] 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 filesCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Related issues
Fixes #23272