'Failed to connect to Jaeger agent: context deadline exceeded' – Jaeger UDP sender initialization

Goal: Verify whether the Jaeger Thrift UDP sender automatically retries sending spans when the agent is temporarily unavailable, so that integration tests can rely on consistent span export without configuring a production Jaeger instance.

Constraints: The client documentation does not specify retry behavior for UDP transmissions, and observed logs show a "context deadline exceeded" error without indication of retry attempts. This uncertainty makes it difficult to decide whether to depend on UDP delivery in flaky test environments or to switch to an alternative sender.

• Does the Jaeger UDP sender perform automatic retries on transient send failures?
• If retries are not performed, what configuration or pattern should be used to achieve reliable span export in tests?
• Is enabling the HTTP sender with a NoopTracer or mock collector a safer approach for credential‑free test suites?