Default sampler behavior changes in OpenTelemetry Java SDK v1.20.0-v1.24.0 affecting trace completeness
0 reputation · 31 May 2023, 21:59 UTC
Default Sampler Behavior Changes in OpenTelemetry Java SDK
The OpenTelemetry Java SDK underwent a significant change in default sampler behavior between versions 1.20.0 and 1.24.0. Applications deployed in production environments without explicitly configuring a sampler may experience unexpected changes in trace completeness and sampling rates.
This behavior shift represents a breaking change for applications that previously relied on undocumented default sampling behavior. The change affects how traces are sampled and exported, potentially impacting observability and debugging capabilities in production systems.
Key concerns include: applications with implicit sampler dependencies may lose trace data; migration requires explicit sampler configuration; version-specific behavior differences complicate upgrade paths; default settings may not align with production observability requirements.
Which default sampler should be explicitly configured to maintain consistent trace completeness across SDK versions v1.20.0 through v1.24.0, and what configuration approach ensures production-ready sampling behavior without relying on undocumented defaults?