Update data-model.asciidoc #4233
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Per the PR and changelogs, the `error.custom` and `transaction.custom` fields were changed to the `flattened` type, but it does not reflect the change in this document. - PR: [#12102](elastic/apm-server#12102) - Changelogs: [APM Release Notes 8.12](https://www.elastic.co/guide/en/observability/current/apm-release-notes-8.12.html#_added_7) In addion, the documentation describes these fields as "non-indexed." In SF case 01746372, the customer reported that these fields are searchable in Discover within Kibana, indicating they may actually be indexed.
|
A documentation preview will be available soon. Request a new doc build by commenting
If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here. |
Maybe @axw can confirm that the field is not indexed. 👋 |
|
The use of |
bmorelli25
added
the
backport-8.x
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Per the PR and changelogs, the
error.customandtransaction.customfields were changed to theflattenedtype since8.12.0, but it does not reflect the change in this document.In addition, the documentation describes these fields as "non-indexed." In SF case 01746372, the customer reported that these fields are searchable in Discover within Kibana, indicating they may actually be indexed.