Consistently map message field in windows integrations #2008
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?
integration
Use ECS mapping for
message
in all.Checklist
- [ ] I have verified that all data streams collect metrics or logs.changelog.yml
file.- [ ] If I'm introducing a new feature, I have modified the Kibana version constraint in my package'smanifest.yml
file to point to the latest Elastic stack release (e.g.^7.13.0
).How to test this PR locally
elastic-package test
Related issues
System
integration doesn't mapmessage
as atext
field for some data streams #1736Windows
integration doesn't mapmessage
astext
for some data streams #1737