You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/product/explore/trace-explorer/index.mdx
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ The [**Trace Explorer**](https://sentry.io/orgredirect/organizations/:orgslug/tr
15
15
- A trace represents a series of transactions or requests through a single system. This includes things like user browser sessions, HTTP requests, DB queries, middleware, caches and more.
16
16
- It captures a series of operations (_spans_) that show how different parts of your application interacted during each transaction.
17
17
- Each trace is identified by a **Trace ID**, which you can use to follow a request across services or projects.
18
-
- A [distributed trace](/platforms/javascript/tracing/trace-propagation/#what-is-distributed-tracing) is made of transactions and spans that traverse multiple servers, clients, edge workers, etc. and is assembled by passing the Trace ID through browser headers.
18
+
- A [distributed trace](/platforms/javascript/tracing/trace-propagation/#what-is-distributed-tracing) is made of transactions and spans that traverse multiple servers, clients, edge workers, and other parts of your system. It is assembled by passing the Trace ID through browser headers.
19
19
20
20
### Spans
21
21
@@ -26,7 +26,7 @@ The [**Trace Explorer**](https://sentry.io/orgredirect/organizations/:orgslug/tr
26
26
27
27
### Span Metrics
28
28
29
-
-[Span metrics](/concepts/key-terms/tracing/span-metrics/) are derived from applying a function to your span attributes (default or custom), like `p50(cart.value)` or `sum(ai.token_use)`, over a granular time frame. This calculation extrapolates metrics that then populate dashboards, alerts, etc. based on that rolling time window.
29
+
-[Span metrics](/concepts/key-terms/tracing/span-metrics/) are derived from applying a function to your span attributes (default or custom), like `p50(cart.value)` or `sum(ai.token_use)`, over a granular time frame. This calculation extrapolates metrics that then populate dashboards and alerts. based on that rolling time window.
30
30
- These 'metrics' aren't stored separately from your span data. Rather, they're queried on the fly. This reduces your need to manage, ingest, and store custom metrics.
31
31
32
32
## Practical Examples
@@ -47,7 +47,7 @@ With these tools, the new Trace Explorer gives you powerful ways to understand y
47
47
Trace Explorer allows you to browse span and trace samples and inspect them. Here's how:
48
48
49
49
1.**Search for Samples**:
50
-
- Use the search bar to filter results based on default or custom attributes, tags, etc. like `http.request_method is "GET`
50
+
- Use the search bar to filter results based on default or custom attributes, tags, and strings like `http.request_method is "GET`
51
51
-**Edit and add** columns in the span samples table to view any attribute
52
52
-**Sort** by clicking the column header to toggle between ascending and descending
53
53
- Switch between **Span Samples** and **Trace Samples** tabs depending on your focus.
0 commit comments