Skip to content

Commit

Permalink
Update trace view to trace details to reflect UI changes (#10201)
Browse files Browse the repository at this point in the history
Update this docs page to reflect the new name.
  • Loading branch information
lizokm committed Jun 2, 2024
1 parent ff62376 commit 0330909
Showing 1 changed file with 9 additions and 7 deletions.
16 changes: 9 additions & 7 deletions docs/concepts/key-terms/tracing/trace-view.mdx
Original file line number Diff line number Diff line change
@@ -1,14 +1,16 @@
---
title: "Trace View"
title: "Trace Details"
sidebar_order: 30
description: "Learn more about trace view, where you can drill down into the details of a single trace, allowing you to debug slow services, identify related errors, and find other bottlenecks."
redirect_from:
- /concepts/key-terms/tracing/trace-view/
description: "Learn more about the trace details page, where you can drill down into the details of a single trace, allowing you to debug slow services, identify related errors, and find other bottlenecks."
---

The trace view is designed to be your one-stop-shop when debugging performance or errors. It gives you full context on what was happening when an error or performance issue occurred, all in one place. The waterfall trace view allows you to see everything that may have occurred during a trace, including errors, performance issues, and any profiles that may have been collected.
The trace details page is designed to be your one-stop-shop when debugging performance or errors. It gives you full context on what was happening when an error or performance issue occurred, all in one place. The waterfall trace details view allows you to see everything that may have occurred during a trace, including errors, performance issues, and any profiles that may have been collected.

In addition, the trace view allows you to drill down into the details of a single trace so you can visualize the high-level transactions and spans that took place within that trace. This makes debugging slow services, identifying related errors, and rooting out bottlenecks easier and faster, since you no longer have to navigate around multiple pages of the Sentry product.
In addition, looking at trace details allows you to drill down into a single trace so you can visualize the high-level transactions and spans that took place within that trace. This makes debugging slow services, identifying related errors, and rooting out bottlenecks easier and faster, since you no longer have to navigate around multiple pages of the Sentry product.

## Product Walkthrough: Trace View Page
## Product Walkthrough: Trace Details Page

Sentry's default visualization of a trace is a waterfall-like structure, where the entries (transactions and spans) in the list are organized chronologically and through ancestry (child spans will fall under their parents). This allows you to follow the order of operations and drill into sub-operations.

Expand Down Expand Up @@ -87,7 +89,7 @@ If you're doing a comparison and want an easy way to go back and forth between h
</div>
<br />
Sometimes, duration gaps between entries can be small, but critical to your debugging
effort. That's why the trace view enables you to zoom into certain areas of the trace,
effort. That's why the trace details view enables you to zoom into certain areas of the trace,
either by double clicking on row elements (which zooms into the row) or by using
your scroll wheel.
<br />
Expand Down Expand Up @@ -120,7 +122,7 @@ your scroll wheel.
></iframe>
</div>
<br />
The trace view has other features like search, which makes it easy to visualize matching
The trace details view has other features like search, which makes it easy to visualize matching
spans that you can then iterate over using the up or down arrows. You can also tailor
the layout to your preference.

Expand Down

0 comments on commit 0330909

Please sign in to comment.