ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Remote sampling configuration scope I am configuring centralized remote sampling for Jaeger, where client libraries poll the collector's /sampling endpoint for their strategy. The strategy is defined in a file mounted into the collector (via a ConfigMap in a Kubernetes/Operator deployment), and the goal is for all services to adopt updated per-service probab
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
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
During a recent deployment, a critical JavaScript error appeared in user sessions. Clarity’s Session Replay captures interactions, but the default 10% sample rate may miss the affected sessions. Raising the sample rate could improve visibility, yet it raises concerns about page load performance and the volume of data retained for analysis. Additionally, the
jaegertracing
opentelemetry
clarity