Skip to content
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

doc(trace-view): Missing trace can be caused by sample rate #3988

Merged
merged 2 commits into from
Aug 6, 2021
+1 −0
Merged

doc(trace-view): Missing trace can be caused by sample rate #3988

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ab0ef7b
doc(trace-view): Missing trace can be caused by sample rate
Zylphrex Aug 5, 2021
528cc48
Update src/docs/product/sentry-basics/tracing/trace-view.mdx
Zylphrex Aug 6, 2021
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
1 change: 1 addition & 0 deletions src/docs/product/sentry-basics/tracing/trace-view.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down