ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Head sampling drops traces before knowing if they matter. Tail sampling in the OpenTelemetry Collector waits for the whole trace -- here's how to configure it and what it costs.
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
I'm designing the tracing pipeline for a set of services that will export OpenTelemetry spans through a Collector, and I need to pick a sampling strategy before rollout. The two documented options pull in opposite directions. With head-based sampling (for example a ParentBased sampler wrapping TraceIdRatioBased in the SDK), the decision happens at span creat
opentelemetry