ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #opentelemetry
The goal is to configure OpenTelemetry alerts so that batch span export reduces network chatter without causing missed or false alerts in SDK version 1.25.x. Key constraints include ambiguous sampler precedence, version‑dependent batch export behavior, and the inability to set per‑resource exporter retry policies, which together make it unclear how to tune a
The goal is to define a consistent expectation for graceful cancellation and timeout handling when using OpenTelemetry SDKs with OTLP exporters and a BatchSpanProcessor. Context cancellation in the application is propagated to in-flight operations but ending a span does not cancel its queued export. Export attempts are bounded by the exporter timeout setting
The OpenTelemetry Collector operates as a stateless intermediary, exporting telemetry via OTLP to various storage backends like ClickHouse or Prometheus. While the collector handles data buffering and retry logic, it lacks native mechanisms to verify the integrity of data sets after a backend-side backup restoration has occurred. Because the collector typica
The same project needs to behave consistently on developer machines, in CI and after deployment. Which versions, dependencies and configuration should be recorded?
Goal Determine whether the OpenTelemetry Specification should require SDKs to automatically populate a process.runtime.description resource attribute, given that current implementations differ and the spec leaves it optional. Constraints and Uncertainty The attribute is not mandated, so some SDKs include it while others omit it, leading to inconsistent resou
An upgrade needs a compatibility check, a tested release and a recovery path. Which changes deserve particular attention before the new version reaches production?
Diagnosing intermittent connection pool exhaustion in high-throughput Java applications requires a balance between visibility and performance overhead. OpenTelemetry provides two primary paths for capturing this telemetry. Automatic Instrumentation The OpenTelemetry Java Agent provides out-of-the-box visibility into JDBC connection pools, capturing span even
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
OpenTelemetry SDK releases have altered the default transport for OTLP exporters across minor versions and language implementations, creating a compatibility boundary for collectors that must support both gRPC and HTTP/protobuf endpoints. When no explicit protocol configuration is provided, the SDK selects a default that may differ from the collector's expec