Fix the experimental OpenTelemetry formatter, so its payload method coerces values. #319
+32
−1
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.
Ensures every attribute value is OTLP‑compatible. Hashes become a JSON string,
nilis dropped, arrays become arrays of strings/numbers/bools.Description of changes
This PR updates the
OpenTelemetryformatter to ensure that all values in the log payload are compatible with the OpenTelemetry Protocol (OTLP) specification for log attributes.The changes introduce methods, to recursively sanitize the payload hash.
The coercion rules are as follows:
String,Integer,Float,Boolean) are passed through unchanged.nilvalues are dropped from the payload.Arrayvalues are sanitized to ensure they only contain OTLP-compatible scalar types.Hashvalues are converted into a JSON string.This prevents potential errors when exporting logs to an OpenTelemetry collector by guaranteeing that all attributes adhere to the expected format. Example errors:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Related to