ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #opentelemetry
A failure needs to be narrowed down before settings are changed or operations retried. Which evidence best separates application errors from environment and dependency problems?
Determine whether OpenTelemetry should provide a dedicated API for configuring timeouts on individual spans, rather than relying exclusively on context‑propagated deadlines. The specification leaves the exact moment a span is considered “ended” versus “aborted” to each SDK implementation, leading to differences in recorded duration and attributes after a can
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