Skip to content

docs: recommend trace sampling in production #85

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
lesnik512 merged 1 commit into from
Oct 16, 2026
+10 −0
Merged

docs: recommend trace sampling in production #85

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
10 changes: 10 additions & 0 deletions readme.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,16 @@ Authentication is intentionally omitted: pick the scheme that fits your project
just --list
```

## Tracing in production
Setting `OPENTELEMETRY_ENDPOINT` turns tracing on, and by default every request is traced. In a benchmark of `GET /api/decks/{id}/`, that cut throughput by about 40%. Sampling with the standard OpenTelemetry variables brings that down to about 20%:

```bash
OTEL_TRACES_SAMPLER=parentbased_traceidratio
OTEL_TRACES_SAMPLER_ARG=0.1
```

This keeps one trace in ten, and follows the caller's decision when a request arrives with a trace context. Errors still reach Sentry when `SENTRY_DSN` is set.

## 📝 [License](https://github.com/modern-python/fastapi-sqlalchemy-template/blob/main/LICENSE)

## Part of `modern-python`
Expand Down
Loading