OTLPv1.6.0

29 Apr 2025since v1.5.0

0 breaking19 notable15 editorial

From the upstream release notes

resource: Add EntityRef. #635
general: add specs for empty telemetry envelopes. #622
logs: Stabilize event_name field in LogRecord message. #643
profiles: Move the lookup tables to ProfilesData. #644
profiles: Move default sample_type from the string table to sample_type. #620
general: remove comment on each service about keeping the RPC alive #637
metrics: clarify when bucket_counts array may be empty #619

Read the full release notes

Notable19

field removedfieldopentelemetry.proto.profiles.v1development.Profile.attribute_tableField 7 (opentelemetry.proto.common.v1.KeyValue) removed.
field removedfieldopentelemetry.proto.profiles.v1development.Profile.attribute_unitsField 8 (AttributeUnit) removed.
field removedfieldopentelemetry.proto.profiles.v1development.Profile.default_sample_type_strindexField 16 (int32) removed.
field removedfieldopentelemetry.proto.profiles.v1development.Profile.function_tableField 6 (Function) removed.
field removedfieldopentelemetry.proto.profiles.v1development.Profile.location_tableField 4 (Location) removed.
field removedfieldopentelemetry.proto.profiles.v1development.Profile.mapping_tableField 3 (Mapping) removed.
field removedfieldopentelemetry.proto.profiles.v1development.Profile.string_tableField 10 (string) removed.
renumberedfieldopentelemetry.proto.profiles.v1development.Profile.attribute_indicesField number changed from 22 to 14. Every previously encoded message decodes wrongly.
renumberedfieldopentelemetry.proto.profiles.v1development.Profile.comment_strindicesField number changed from 15 to 8. Every previously encoded message decodes wrongly.
renumberedfieldopentelemetry.proto.profiles.v1development.Profile.dropped_attributes_countField number changed from 19 to 11. Every previously encoded message decodes wrongly.
renumberedfieldopentelemetry.proto.profiles.v1development.Profile.duration_nanosField number changed from 12 to 5. Every previously encoded message decodes wrongly.
renumberedfieldopentelemetry.proto.profiles.v1development.Profile.location_indicesField number changed from 5 to 3. Every previously encoded message decodes wrongly.
renumberedfieldopentelemetry.proto.profiles.v1development.Profile.original_payloadField number changed from 21 to 13. Every previously encoded message decodes wrongly.
renumberedfieldopentelemetry.proto.profiles.v1development.Profile.original_payload_formatField number changed from 20 to 12. Every previously encoded message decodes wrongly.
renumberedfieldopentelemetry.proto.profiles.v1development.Profile.periodField number changed from 14 to 7. Every previously encoded message decodes wrongly.
renumberedfieldopentelemetry.proto.profiles.v1development.Profile.period_typeField number changed from 13 to 6. Every previously encoded message decodes wrongly.
renumberedfieldopentelemetry.proto.profiles.v1development.Profile.profile_idField number changed from 17 to 10. Every previously encoded message decodes wrongly.
renumberedfieldopentelemetry.proto.profiles.v1development.Profile.time_nanosField number changed from 11 to 4. Every previously encoded message decodes wrongly.
field renamedfieldopentelemetry.proto.profiles.v1development.Profile.link_tableRenamed to default_sample_type_index (field 9 unchanged). Binary OTLP is unaffected; OTLP/JSON keys on the name.

Editorial15

new rulerequirementdocs/specification.md#empty-telemetry-envelopesSHOULD NOT added: Given that, senders SHOULD NOT create empty envelopes (OTLP payloads that contain zero spans, zero metric points or zero log records), receivers MAY ignore empty envelopes, and implementations that receive and send (for...
rewordedrequirementdocs/specification.md#otlphttp-throttlingSHOULD reworded: If the client receives a retryable error code (see table above) and the "Retry-After" header is not present in the response, then the client SHOULD implement an exponential backoff strategy between r...
movedrequirementdocs/specification.md#retryable-response-codesSHOULD moved here from "failures-1": The requests that receive a response status code listed in following table SHOULD be retried.
movedrequirementdocs/specification.md#retryable-response-codesMUST NOT moved here from "failures-1": All other 4xx or 5xx response status codes MUST NOT be retried.
addedsectiondocs/specification.md#empty-telemetry-envelopesNew section "Empty Telemetry Envelopes".
addedsectiondocs/specification.md#retryable-response-codesNew section "Retryable Response Codes".
addedmessageopentelemetry.proto.common.v1.EntityRefA reference to an Entity. Entity represents an object of interest associated with produced telemetry: e.g spans, metrics, profiles, or logs. Status: [Development]
field addedfieldopentelemetry.proto.profiles.v1development.ProfilesData.attribute_tableField 7, repeated opentelemetry.proto.common.v1.KeyValue.
field addedfieldopentelemetry.proto.profiles.v1development.ProfilesData.attribute_unitsField 8, repeated AttributeUnit.
field addedfieldopentelemetry.proto.profiles.v1development.ProfilesData.function_tableField 4, repeated Function.
field addedfieldopentelemetry.proto.profiles.v1development.ProfilesData.link_tableField 5, repeated Link.
field addedfieldopentelemetry.proto.profiles.v1development.ProfilesData.location_tableField 3, repeated Location.
field addedfieldopentelemetry.proto.profiles.v1development.ProfilesData.mapping_tableField 2, repeated Mapping.
field addedfieldopentelemetry.proto.profiles.v1development.ProfilesData.string_tableField 6, repeated string.
field addedfieldopentelemetry.proto.resource.v1.Resource.entity_refsField 3, repeated opentelemetry.proto.common.v1.EntityRef.