Crate Name
datadog-opentelemetry
Crate Version(s)
0.4.0
Describe the goal of the feature
Bump the OpenTelemetry stack from 0.31 to 0.32 in the workspace, so datadog-opentelemetry can be used on 32-bit targets that lack native 64-bit atomics.
Concretely:
opentelemetry, opentelemetry_sdk, opentelemetry-otlp, opentelemetry-semantic-conventions: 0.31.0 → 0.32 (workspace root Cargo.toml, the pins the published crate inherits).
- dev/example/bridge deps for consistency:
tracing-opentelemetry 0.32 → 0.33 (the release paired with otel 0.32), opentelemetry-appender-log/opentelemetry-appender-tracing/opentelemetry-stdout/opentelemetry-http 0.31 → 0.32.
Is your feature request related to a problem?
We wish to make datadog work on 32-bit platform
Describe alternatives you've considered
We dropped datadog-opentelemetry and rebuilt the pipeline directly on opentelemetry + opentelemetry-otlp 0.32 — OTLP/HTTP with a custom blocking HttpClient, exporting to a local Datadog Agent's OTLP receiver. It works and compiles on the 32-bit target, but it means maintaining the integration ourselves and forgoing the Datadog-specific layer the wrapper provides (sampling, propagation, span/resource mapping, native trace export to the Agent). A version bump would let us return to the wrapper.
Additional context
No response
Crate Name
datadog-opentelemetry
Crate Version(s)
0.4.0
Describe the goal of the feature
Bump the OpenTelemetry stack from
0.31to0.32in the workspace, sodatadog-opentelemetrycan be used on 32-bit targets that lack native 64-bit atomics.Concretely:
opentelemetry,opentelemetry_sdk,opentelemetry-otlp,opentelemetry-semantic-conventions:0.31.0→0.32(workspace rootCargo.toml, the pins the published crate inherits).tracing-opentelemetry0.32→0.33(the release paired with otel0.32),opentelemetry-appender-log/opentelemetry-appender-tracing/opentelemetry-stdout/opentelemetry-http0.31→0.32.Is your feature request related to a problem?
We wish to make datadog work on 32-bit platform
Describe alternatives you've considered
We dropped
datadog-opentelemetryand rebuilt the pipeline directly onopentelemetry+opentelemetry-otlp0.32 — OTLP/HTTP with a custom blockingHttpClient, exporting to a local Datadog Agent's OTLP receiver. It works and compiles on the 32-bit target, but it means maintaining the integration ourselves and forgoing the Datadog-specific layer the wrapper provides (sampling, propagation, span/resource mapping, native trace export to the Agent). A version bump would let us return to the wrapper.Additional context
No response