Move setting of destination.ip to ingest pipeline #5695
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
For spans, we copy
destination.address
todestination.ip
if the value is a valid IPv4 or IPv6 address. Move this from model transformation to the Elasticsearch ingest pipeline, to remove logic from model transformation code.Checklist
- [ ] Update CHANGELOG.asciidoc- [ ] Documentation has been updatedHow to test these changes
Send some spans to APM Server with destination address set, and check that
destination.address
is copied (or not) todestination.ip
depending on whether it is a valid IPv4 or IPv6 address.Related issues
#3565