OTLPv1.11.1
since v1.11.00 breaking0 notable5 editorial
From the upstream release notes
- docs: clarify UTF-8 handling requirements. #845
- examples: update attribute examples to use the latest semantic conventions. #853
- all: document the version in which every protobuf field was introduced and require since <version> comments for new fields. #854
- openapi: Update OpenAPI generation to use integer-based enums. #841
- docs: clarify that OTLP JSON timestamps are integer values and not RFC 3339 strings. #855
Editorial5
- new rulerequirementdocs/specification.md#utf-8-string-handlingSHOULD added: Encoders SHOULD ensure
stringfields contain valid UTF-8. - new rulerequirementdocs/specification.md#utf-8-string-handlingSHOULD added: Decoders SHOULD be prepared to receive non-compliant strings from permissive runtimes and SHOULD replace invalid UTF-8 sequences (code units) with the Unicode replacement character (
U+FFFD). - new rulerequirementdocs/specification.md#utf-8-string-handlingMAY added: Intermediary nodes (such as the OpenTelemetry Collector) are not required to perform in-line UTF-8 validation on
stringfields and MAY pass them through without inspection. - new rulerequirementdocs/specification.md#utf-8-string-handlingMAY added: Intermediary components MAY provide optional, configurable validation or sanitization.
- addedsectiondocs/specification.md#utf-8-string-handlingNew section "UTF-8 String Handling".