Skip to content

Commit e6ee0b8

Browse files
mplorentzlizokm
andauthored
Fix broken link to profile page (#11564)
* Fix broken link to profile page * Update docs/concepts/key-terms/tracing/distributed-tracing.mdx --------- Co-authored-by: Liza Mock <[email protected]>
1 parent c6de652 commit e6ee0b8

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/concepts/key-terms/tracing/distributed-tracing.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ Distributed tracing provides a connected view of your application from frontend
1616

1717
A tracing tool focuses on what happened (and when), logging events during a program's execution across multiple systems. Traces often include timestamps, allowing durations to be calculated, but their purpose is broader, showing how interconnected systems interact and how problems in one can affect another. While tracing can be useful if instrumented in just the frontend or backend, it's most powerful when set up for your full stack (distributed tracing).
1818

19-
It's important to note that tracing is not [profiling](https://github.com/product/explore/profiling/). A profiler measures various aspects of an application's operation, resulting in a statistical summary. While both diagnose application problems, they differ in what they measure and how data is recorded.
19+
It's important to note that tracing is not [profiling](/product/explore/profiling/). A profiler measures various aspects of an application's operation, resulting in a statistical summary. While both diagnose application problems, they differ in what they measure and how data is recorded.
2020

2121

2222
Learn more in this [Tracing: Frontend issues with backend solutions](https://sentry.io/resources/tracing-frontend-issues-with-backend-solutions/?original_referrer=https%3A%2F%2Fblog.sentry.io%2F) workshop.

0 commit comments

Comments
 (0)