OpenTelemetry defaults to parentbased_always_on, but this is not consistent across our distributions:
parentbased_always_on is used by Node.js, .NET, Python
always_on is used by Java
If we are advertising as a no sampling solution, we should default to always_on, but still allow for customers to change it.
Using parentbased_always_on can cause data loss if customers have previously set up cloud tracing, which injects a traceparent with 00 for traceflags.
OpenTelemetry defaults to
parentbased_always_on
, but this is not consistent across our distributions:parentbased_always_on
is used by Node.js, .NET, Pythonalways_on
is used by JavaIf we are advertising as a no sampling solution, we should default to
always_on
, but still allow for customers to change it. Usingparentbased_always_on
can cause data loss if customers have previously set up cloud tracing, which injects atraceparent
with00
fortraceflags
.