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.
Deciding between OneAgent SDK and OpenTelemetry for custom metrics? Learn the trade-offs between native integration and vendor-neutrality to optimize your Dynatrace observability.
A practical guide to configuring OpenTelemetry Collector for reliable OTLP export with batching, retry backoff and dead letter handling to prevent silent telemetry loss.
Resource Attribute Handling in OTLP Pipelines The OpenTelemetry Collector utilizes a pipeline architecture where telemetry signals are passed from receivers through processors to exporters. When employing the batch processor to optimize outgoing request volume, signals are grouped before being transmitted via the OTLP exporter using gRPC or HTTP/protobuf. A
The OpenTelemetry OTLP exporter resolves the collector endpoint via the system DNS resolver before establishing a TLS connection. When the hostname cannot be resolved, the exporter logs an error and ceases sending telemetry until the application is restarted. Likewise, a failed TLS handshake due to an invalid or self‑signed certificate results in an immediat
When a request context is cancelled while an OpenTelemetry span is still active, the SDK is expected to end the span, but the exact moment of span completion relative to the cancellation signal varies between language implementations. The OpenTelemetry Specification defines cancellation propagation but does not prescribe how instrumentation should record par
jaegertracing
java
dynatrace