Skip to content

Commit 2df08b9

Browse files
committed
add tracing section
1 parent 0c7ae64 commit 2df08b9

File tree

2 files changed

+18
-0
lines changed

2 files changed

+18
-0
lines changed
237 KB
Loading

docs/product/tracing/index.mdx

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,8 @@ description: "Learn about using tracing and distributed tracing for observing an
88

99
Tracing is the process of capturing the timing and flow of requests and operations as they happen throughout your application. It can be a powerful debugging tool, helping you identify which link in a sequence of events is causing a problem.
1010

11+
![An image of a trace with spans.](./img/The-anatomy-of-a-trace.png)
12+
1113
### What's Distributed Tracing?
1214

1315
Distributed tracing provides a unified view of how a single request moves from the frontend to the backend and beyond. This is particularly useful in modern applications, which are often composed of multiple services working together. To get a distributed view of your application, instrument Sentry in both your frontend and your backend.
@@ -24,3 +26,19 @@ A span is a named, timed operation that represents a part of the application wor
2426
### What's a Transaction?
2527

2628
Transactions are a Sentry-specific unit of measurement that references any event that users send to Sentry. In addition to standard event fields, transactions also contains child spans and have a unique transaction ID.
29+
30+
## How to Use Tracing in Sentry
31+
32+
To get the most out of tracing in Sentry, you'll need to instrument both the frontend and backend of your application with Sentry's SDK. Once this is done, there are several places where you can view and interact with tracing data:
33+
34+
**Explore to Traces to Trace View**
35+
36+
You can view all the traces in your organization by going to the [Traces](https://sentry.io/orgredirect/organizations/:orgslug/traces/) page in Sentry. You'll see a chart and a list of traces and be able to see at-a-glance how long each trace took to complete and the number of spans it contains.
37+
38+
If you want more information, click on any trace ID. This will take you to the [Trace View](https://sentry.io/orgredirect/organizations/:orgslug/traces/:traceid/) page, which provides a more detailed view of the trace and its spans. Here, you'll see a waterfall view of the spans in the trace, which will show you how long each service and process took to complete and may give you an indicator of where a problem may be coming from. Learn more about the Sentry [Trace View](/platform/explore/trace-view/).
39+
40+
Alternatively, you can use the search bar to look for traces by name, project, or other criteria. You can also use the tags section to filter traces by specific tags. Learn more about the Sentry [Trace Explorer](/platform/explore/trace-explorer/).
41+
42+
**Performance to Trace View**
43+
44+
If you're interested in a high-level view of your application's performance, you can start from the [Performance](https://sentry.io/orgredirect/organizations/:orgslug/performance/) page in Sentry where you'll see a list of transactions. Clicking on the transaction ID will take you to the Trace View page for that transaction. Learn more about using Sentry's [Performance Monitoring](/platform/performance-monitoring/).

0 commit comments

Comments
 (0)