-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Filebeat] Update Elasticsearch Deprecation fileset parsing #26880
[Filebeat] Update Elasticsearch Deprecation fileset parsing #26880
Conversation
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
/test |
This pull request is now in conflicts. Could you fix it? 🙏
|
Pinging @elastic/integrations (Team:Integrations) |
/test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, this will have to be changed in integrations too. cc @sayden
* #26857: Update Elasticsearch Deprecation fileset parsing * update changelog Co-authored-by: Marc Guasch <[email protected]> (cherry picked from commit a25a244)
* #26857: Update Elasticsearch Deprecation fileset parsing * update changelog Co-authored-by: Marc Guasch <[email protected]> (cherry picked from commit a25a244)
…27095) * #26857: Update Elasticsearch Deprecation fileset parsing * update changelog Co-authored-by: Marc Guasch <[email protected]> (cherry picked from commit a25a244) Co-authored-by: Alex Resnick <[email protected]>
* #26857: Update Elasticsearch Deprecation fileset parsing * update changelog Co-authored-by: Marc Guasch <[email protected]> (cherry picked from commit a25a244)
…27096) * #26857: Update Elasticsearch Deprecation fileset parsing * update changelog Co-authored-by: Marc Guasch <[email protected]> (cherry picked from commit a25a244) Co-authored-by: Alex Resnick <[email protected]>
What does this PR do?
Update the ingest pipelines for the Elasticsearch's deprecation logs.
Why is it important?
The current pipelines are parsing incorrectly or dropping events due to changes in the deprecation log format.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Author's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs