Ingest structured ES deprecation logs #10445
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
enhancement
module
review
Filebeat
|
Pinging @elastic/stack-monitoring |
|
/cc @pgomulka for awareness |
ruflin
reviewed
Jan 31, 2019
filebeat/module/elasticsearch/deprecation/test/elasticsearch_deprecation.log-expected.json
Show resolved
Hide resolved
|
@ruflin Rebased and addressed review feedback. Ready for another pass, when you have a chance. Thanks! |
ruflin
approved these changes
Feb 1, 2019
cachedout
approved these changes
Feb 1, 2019
|
jenkins, test this |
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.
This PR teaches the
elasticsearch/deprecationfileset to ingest structured Elasticsearch deprecation logs.This PR takes the same approach as #10352, in that it creates an entrypoint pipeline,
pipeline.json, that delegates further processing of a log entry depending on what it sees as the first character of the entry:{, it assumes the log line is structured as JSON and delegates further processing topipeline-json.json.pipeline-plaintext.json.