Skip to content

Add an FAQ to trace propagation cheat sheet #13528

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
merged 2 commits into from
Apr 28, 2025
Merged

Add an FAQ to trace propagation cheat sheet #13528

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
15ea5a2
Add an FAQ to trace propagation cheat sheer
sentrivana Apr 28, 2025
44ccf8d
Update trace-propagation-cheat-sheet.mdx
sentrivana Apr 28, 2025
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
6 changes: 6 additions & 0 deletions develop-docs/sdk/telemetry/traces/trace-propagation-cheat-sheet.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,3 +37,9 @@ This is a cheat sheet where you can see how the trace propagation work in SDKs i
| present | 0 | no | null | no | no | - |
| present | 0 | no | 0 | no | no | - |
| present | 0 | no | 1 | no | no | - |

## FAQ

**Why are we sometimes sampling even if `traces_sample_rate` is 0? Why are we sometimes unsampling if `traces_sample_rate` is 1?**

A `traces_sample_rate` between 0 and 1 is only taken into account if there is no incoming trace and the SDK has to make its own sampling decision. If there is an incoming trace, the parent sampling decision always takes precedence over `traces_sample_rate`.