Jaeger Remote Sampling Transition to Static Local Sampling Behavior

Jaeger Tracing Sampling

A configuration utilizing a static local sampler functions correctly in a local development environment.

Production Sampling Failure

This same setup results in zero sampled traces when deployed to production infrastructure.

What is the documented fallback behavior of Jaeger client libraries when the remote sampling endpoint is unreachable in a production network context?

• Does the client strictly adhere to the static local configuration, or does it enter an undefined state?
• What specific client library versions guarantee a non-zero sampling rate upon remote endpoint failure?