fix(otel_otlp_logs): encode log record body as string instead of int array #952
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.
Description
Currently, log record bodies are encoded as integer arrays before exporting. This causes downstream log backends to render the logs as raw byte lists rather than human-readable text strings.

e.g.,
This change switches the regex replacement to use
{return, binary}, ensuring the exporter generates astring_value.Root cause
As seen in the shell output below,
otel_otlp_common:to_any_value/1converts a list string into anarray_valueof integers, while a binary becomes astring_value.