Add pattern to handle logs from newer ES versions #17406
Merged
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
ycombinator
added
bug
Filebeat
|
Pinging @elastic/stack-monitoring (Stack monitoring) |
ycombinator
added
Team:Services
|
Pinging @elastic/integrations-services (Team:Services) |
ycombinator
added
[zube]: In Review
needs_backport
zube
bot
removed
needs_backport
kaiyan-sheng
approved these changes
Apr 1, 2020
narph
approved these changes
Apr 1, 2020
|
@elasticmachine run elasticsearch-ci/docs |
ycombinator
added a commit
to ycombinator/beats
that referenced
this pull request
Apr 1, 2020
* Add pattern to handle logs from newer ES versions * Adding CHANGELOG entry
This was referenced Apr 1, 2020
ycombinator
added a commit
to ycombinator/beats
that referenced
this pull request
Apr 1, 2020
* Add pattern to handle logs from newer ES versions * Adding CHANGELOG entry
ycombinator
added a commit
to ycombinator/beats
that referenced
this pull request
Apr 2, 2020
* Add pattern to handle logs from newer ES versions * Adding CHANGELOG entry
|
@ycombinator Hello, I just want to stress that this a bug with a huge impact. As the audit logs are enormous, the result is the clusters receiving these logs are not able to parse the timestamp which results in very heavy load and all kinds of issues. |
ycombinator
added a commit
that referenced
this pull request
Apr 3, 2020
ycombinator
added a commit
that referenced
this pull request
Apr 3, 2020
ycombinator
added a commit
that referenced
this pull request
Apr 3, 2020
leweafan
pushed a commit
to leweafan/beats
that referenced
this pull request
Apr 28, 2023
…astic#17422) * Add pattern to handle logs from newer ES versions * Adding CHANGELOG entry
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.
What does this PR do?
Adds another date format pattern to accept dates with or without timezones, as seen in Elasticsearch audit logs. Older versions of Elasticsearch omit the timezone while newer versions introduce it. The change in this PR will allow the ingest pipeline to handle both.
Why is it important?
It fixes a bug introduced in #15942. Due to that bug, users who upgrade to Filebeat 7.6.0 or later are seeing errors like this:
Checklist
I have commented my code, particularly in hard-to-understand areasI have made corresponding changes to the documentationI have made corresponding change to the default configuration filesCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.