Removes body text alias mapping change because OTEL demo updated #113
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
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.
Changes
The OTel demo seems to have updated so that its otel logs no longer ship with
body_text, which we had to account for before, but now withbody.text, which our mappings already account for. So the post-setup script will break our ES env with this mapping change, if the data is flowing in with body.text. We no longer need this mapping update, unless you're running an old version of the OTel demo services.If you still see body_text in your logs-otel documents, kill minikube and re-run the
setupscript, and it should start sending documents with body.text instead.