ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #opentelemetry
Learn how to implement distributed tracing in Java microservices using OpenTelemetry and Jaeger to identify latency bottlenecks and visualize request flows.
Learn how OpenTelemetry’s Java auto‑instrumentation agent provides zero‑code distributed tracing for Spring Boot services, with a concrete setup example and practical limits.
Missing HTTP client spans in OpenTelemetry Java can stem from agent mis‑configuration, exporter limits, or network issues. This diagnostic guide walks through symptoms, checks, fixes, and escalation steps to help you restore full trace visibility.
Jaeger offers constant, probabilistic, rate-limiting, and adaptive sampling. Here's how to choose between them, verify what clients actually received, and when you need tail sampling instead.
Problem OpenTelemetry auto‑instrumentation libraries default to a probability sampler (often 10% for Java, 5% for Python) to limit trace volume. The SDK exposes a sampler configuration API, but changing the sampler at runtime requires code changes or a restart; no cross‑language, environment‑variable override is defined in the core spec. Vendor exporters (Ja
Goal Reduce alert noise when the BatchSpanProcessor logs Failed to export span during brief network hiccups while preserving visibility into real data loss. Constraints The SDK currently lacks a retry configuration, so transient failures are logged immediately and can trigger alerts on every occurrence. Users often rely on the Collector’s retry_on_failure bl
jaegertracing
java