Add-link-to-tracing-workshop (#11009)

* Add-link-to-tracing-workshop * Update docs/concepts/key-terms/tracing/distributed-tracing.mdx Co-authored-by: vivianyentran <[email protected]> --------- Co-authored-by: vivianyentran <[email protected]>
getsentry · Aug 6, 2024 · 70a268d · 70a268d
1 parent ce040f4
commit 70a268d
Showing 1 changed file with 2 additions and 0 deletions.
diff --git a/docs/concepts/key-terms/tracing/distributed-tracing.mdx b/docs/concepts/key-terms/tracing/distributed-tracing.mdx
@@ -18,6 +18,8 @@ A profiler may measure any number of aspects of an application's operation: the
 
 A tracing tool, on the other hand, focuses on _what_ happened (and when), rather than how many times it happened or how long it took. The resulting trace is a log of events which occurred during a program's execution, often across multiple systems. Though traces most often - or, in the case of Sentry's traces, always - include timestamps, allowing durations to be calculated, measuring performance is not their only purpose. They can also show the ways in which interconnected systems interact, and the ways in which problems in one can cause problems in another.
 
+To learn more, watch 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.
+
 ### Why Tracing?
 
 Applications typically consist of interconnected components, which are also called services. As an example, let's look at a modern web application, composed of the following components, separated by network boundaries: