Revert some flattened fields to object type #12157
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
Revert some fields from flattened back to object to align with how we will dynamically map those fields in the future. We keep a few APM-specific fields that may cause mapping conflicts as flattened for now.
Object-type fields:
http.request.env.*
http.request.cookies.*
http.request.headers.*
http.response.headers.*
span.message.headers.*
transaction.message.headers.*
Flattened-type fields:
error.custom
(APM-specific arbitrary object structure)error.exception.attributes
(APM-specific arbitrary object structure)error.exception.stacktrace
(APM-specific structured stack trace)error.log.stacktrace
(APM-specific structured stack trace)http.request.body
(may be either a string or object, and object fields are arbitrary so therefore may cause conflicts)span.stacktrace
(APM-specific structured stack trace)transaction.custom
(APM-specific arbitrary object structure)Checklist
- [ ] Update CHANGELOG.asciidoc- [ ] Update package changelog.yml (only if changes to(reverts an unreleased change made in #12102)apmpackage
have been made)- [ ] Documentation has been updatedHow to test these changes
Related issues
#11528
#11529