Don't set processor.event
for logs
#11494
Merged
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.
Motivation/summary
This is not used in any queried made by the APM UI, and is an APM-specific field that we should phase out. By removing it from logs, we can potentially write logs to non-APM specific log datastreams.
See also elastic/kibana#161718
Checklist
- [ ] Update CHANGELOG.asciidocapmpackage
have been made)- [ ] Documentation has been updatedHow to test these changes
processor.event
fieldRelated issues
elastic/kibana#161718