ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #opentelemetry
Compare suitability, operational responsibilities and limits before choosing this technology for a project. Which trade-offs should guide the decision?
Recovery needs to recreate the working service and its required data after a machine or process is lost. Which artifacts and state need protection, and how should the restore be checked?
A performance change should improve the measured workload without sacrificing correctness or wasting capacity. Which measurements and bottlenecks should be considered first?
The same project needs to behave consistently on developer machines, in CI and after deployment. Which versions, dependencies and configuration should be recorded?
An upgrade needs a compatibility check, a tested release and a recovery path. Which changes deserve particular attention before the new version reaches production?
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
Configuration must be available to the application without exposing credentials in source control, logs or browser code. What belongs in the runtime and which access controls matter?