From 70a268d87c1513b5227271b10095c080a8bb5a02 Mon Sep 17 00:00:00 2001 From: Liza Mock Date: Tue, 6 Aug 2024 16:20:00 -0700 Subject: [PATCH] Add-link-to-tracing-workshop (#11009) * Add-link-to-tracing-workshop * Update docs/concepts/key-terms/tracing/distributed-tracing.mdx Co-authored-by: vivianyentran <20403606+vivianyentran@users.noreply.github.com> --------- Co-authored-by: vivianyentran <20403606+vivianyentran@users.noreply.github.com> --- docs/concepts/key-terms/tracing/distributed-tracing.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/concepts/key-terms/tracing/distributed-tracing.mdx b/docs/concepts/key-terms/tracing/distributed-tracing.mdx index 83a3e6a4601e7..29139555e4bcb 100644 --- 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: