[cisco_aironet] Add support for logs with dual sequence numbers and timezone abbreviations#17271
Open
kgeller wants to merge 5 commits intoelastic:mainfrom
Open
[cisco_aironet] Add support for logs with dual sequence numbers and timezone abbreviations#17271kgeller wants to merge 5 commits intoelastic:mainfrom
kgeller wants to merge 5 commits intoelastic:mainfrom
Conversation
🚀 Benchmarks reportTo see the full report comment with |
|
Pinging @elastic/integration-experience (Team:Integration-Experience) |
💚 Build Succeeded
History
cc @kgeller |
This file contains hidden or 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
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.
Proposed commit message
Adds Grok pattern support for Cisco logs that include dual sequence numbers, explicit hostname fields, and timezone abbreviations, which were previously failing to parse.
Changes:
default.ymlline 20): Added pattern to match<priority>sequence: hostname: sequence: date: messageformat%{WORD:_temp_.raw_date_timezone}instead of%{TZ}for broader compatibility with non-standard abbreviations like SGT\\s+) for more robust date parsingtz_offset: Asia/Singaporeto test config to properly handle timezone abbreviations during date parsingChecklist
changelog.ymlfile.I have verified that any added dashboard complies with Kibana's Dashboard good practices