Skip to content

Commit 632ae99

Browse files
sfanahataShannon Anahata
andauthored
Adding span metrics link to trace explorer docs (#13675)
## DESCRIBE YOUR PR Fixing the linting issue from this branch (#13652) and updating trace explorer docs with a link. ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. - [ ] Urgent deadline (GA date, etc.): <!-- ENTER DATE HERE --> - [ ] Other deadline: <!-- ENTER DATE HERE --> - [ ] None: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it. Thanks in advance for your help! ## PRE-MERGE CHECKLIST *Make sure you've checked the following before merging your changes:* - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) --------- Co-authored-by: Shannon Anahata <[email protected]>
1 parent f121224 commit 632ae99

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/product/explore/trace-explorer/index.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ The [**Trace Explorer**](https://sentry.io/orgredirect/organizations/:orgslug/tr
2626

2727
### Span Metrics
2828

29-
- 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, alerts, etc. based on that rolling time window.
3030
- 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.
3131

3232
## Practical Examples

0 commit comments

Comments
 (0)