Handle ECS-compatible deprecation logs emitted by ES 8.0.0+ #17728
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
3 tasks
ycombinator
added
[zube]: In Review
needs_backport
|
Pinging @elastic/stack-monitoring (Stack monitoring) |
|
Pinging @elastic/integrations-services (Team:Services) |
ycombinator
force-pushed
the
fb-es-deprecation-800-ecs
branch
from
e991c03
to
3c37cb1
Compare
ycombinator
force-pushed
the
fb-es-deprecation-800-ecs
branch
from
3c37cb1
to
2a58251
Compare
|
Travis CI is green and Jenkins CI failures are unrelated. Merging. |
ycombinator
removed
the
needs_backport
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?
With elastic/elasticsearch#47105 merged, starting with 8.0.0, Elasticsearch will emit ECS-compatible deprecation (and other types of) logs. This PR enhances the
elasticsearch/deprecationfileset's ingestion pipeline to handle this new deprecation log format, while also remaining backwards-compatible with the previous (7.x) deprecation log format.Why is it important?
So the Filebeat
elasticsearch/deprecationfileset can handle current as well as upcoming Elasticsearch deprecation log formats.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.Related issues