diff --git a/develop-docs/sdk/telemetry/traces/trace-propagation-cheat-sheet.mdx b/develop-docs/sdk/telemetry/traces/trace-propagation-cheat-sheet.mdx index 614cb426a1f43..f5a1a7756493b 100644 --- a/develop-docs/sdk/telemetry/traces/trace-propagation-cheat-sheet.mdx +++ b/develop-docs/sdk/telemetry/traces/trace-propagation-cheat-sheet.mdx @@ -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`.