[9.2] (backport #18470) Include pipeline and plugin IDs to the JSON logs. #18474
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.
Release notes
Include pipeline and plugin IDs to the JSON logs.
What does this PR do?
Adds pipeline and plugin IDs to the JSON logs.
Why is it important/What is the impact to the user?
It crucial to know which plugin from which pipeline is generating a specific logs, especially errors. For now, when using JSON log format with Logstash, it is hard to figure out where the errors (or particular log lines) are coming from.
After this PR, logs provide more visibility for the case which plugin and pipeline are generating the logs.
Examples,
Checklist
[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files (and/or docker env variables)How to test this PR locally
./gradlew clean bootstrap assemble installDefaultGemslogstash.yml, addlog.format: jsonlinebin/logstash -f config/test.confRelated issues
Use cases
Screenshots
Logs