From ee65415a6c8baf69a2317b3b12aaa144c3a936e2 Mon Sep 17 00:00:00 2001 From: Tony Xiao Date: Fri, 6 Aug 2021 13:13:26 -0400 Subject: [PATCH] doc(trace-view): Missing trace can be caused by sample rate (#3988) * doc(trace-view): Missing trace can be caused by sample rate * Update src/docs/product/sentry-basics/tracing/trace-view.mdx Co-authored-by: Isabel <76437239+imatwawana@users.noreply.github.com> Co-authored-by: Isabel <76437239+imatwawana@users.noreply.github.com> --- src/docs/product/sentry-basics/tracing/trace-view.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/src/docs/product/sentry-basics/tracing/trace-view.mdx b/src/docs/product/sentry-basics/tracing/trace-view.mdx index d0d060ffef5c2..3a79c0ecf8386 100644 --- a/src/docs/product/sentry-basics/tracing/trace-view.mdx +++ b/src/docs/product/sentry-basics/tracing/trace-view.mdx @@ -33,6 +33,7 @@ In a fully instrumented system, a span in one service will connect to a transact In addition, broken subtraces can occur when Sentry receives an error for a trace, but the corresponding transaction does not exist. In this case, the error will not appear on the trace view and the trace navigator won't appear on the **Issue Details** page. In these cases you can click "Open In Discover" to see all the events in the trace. Broken subtraces may be caused by: +- Sample rates may prevent the SDK from sending a transaction, so not all errors will have an associated transaction in Sentry. - [Ad blockers](/platforms/javascript/troubleshooting/#dealing-with-ad-blockers) may prevent transactions in browsers being sent, but HTTP requests to backend projects will still create child transactions - [Rate-limiting](/product/accounts/quotas/#limiting-events) on a project may cause only some events to be sent to Sentry - [Project permissions](/product/accounts/membership/#restricting-access) may mean you do not have access to transactions in another project