Skip to content

docs: correct workers tracing sampling description #81

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ankurs merged 1 commit into from
Apr 27, 2026
Merged

docs: correct workers tracing sampling description #81

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion howto/workers.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -394,7 +394,7 @@ middleware.Recover(func(name string, v any) {

### Tracing

Creates an OTEL span named `worker:<name>:cycle` for each tick. Records errors on the span. Worker spans are always sampled regardless of the global sampler — this prevents silent span drops when using `ParentBased(TraceIDRatioBased(...))`, where worker root spans (which have no incoming parent) would otherwise be probabilistically dropped.
Creates an OTEL span named `worker:<name>:cycle` for each tick. Records errors on the span. Worker spans are typically trace roots (no incoming parent), so sampling is determined by the global `TracerProvider`'s sampler — if you use `ParentBased(TraceIDRatioBased(...))` with a low ratio, worker spans may be probabilistically dropped. Use `AlwaysSample()` for the worker `TracerProvider` if you need every cycle traced.

The OTEL trace ID is automatically injected into the log context as `trace` for correlation with your tracing backend.

Expand Down
Loading