From 53871d67d96ed75501369111199b913c838c0472 Mon Sep 17 00:00:00 2001 From: Liza Mock Date: Sun, 6 Oct 2024 16:56:58 -0700 Subject: [PATCH 1/4] update defs --- docs/product/tracing/index.mdx | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 docs/product/tracing/index.mdx diff --git a/docs/product/tracing/index.mdx b/docs/product/tracing/index.mdx new file mode 100644 index 0000000000000..2e6fda2b4ca55 --- /dev/null +++ b/docs/product/tracing/index.mdx @@ -0,0 +1,26 @@ +--- +title: Tracing +sidebar_order: 20 +description: "Learn about using tracing and distributed tracing for observing and debugging application performance issues. You'll see the impact of errors across your full stack and microservices." +--- + +## Tracing + +Tracing is the process of capturing the timing and flow of requests and operations as they happen throughout your application. It can be a powerful debugging tool, helping you identify which link in a sequence of events is causing a problem. + +### What's Distributed Tracing? + +Distributed tracing provides a unified view of how a single request moves from the frontend to the backend and beyond. This is particularly useful in modern applications, which are often composed of multiple services working together. To get a distributed view of your application, instrument Sentry in both your frontend and your backend. + +With distributed tracing, you can identify performance bottlenecks that are affecting your application no matter where in your application's workflowthey occur. You can then use Sentry tools such as the Trace Explorer or Trace View page to dig deeper and find the root cause of the problem. Distributed tracing is particularly helpful for identifying problems you can't just debug using console logs, such as race conditions, N+1, and caching issues. + +### What's a Trace? + +Each trace has a string of globally unique characters called a trace ID, that's shared by both frontend and backend services they help connect all the actions that take place to make an event such as a button click or a page scroll. Each trace is composed of multiple spans. + +### What's a Span? +A span is a named, timed operation that represents a part of the application workflow. It provides granular insights into specific tasks, like API requests or database queries. Multiple spans are pieced together to create a trace. providing a comprehensive view of its path, timing, and interactions for troubleshooting and performance analysis. + +### What's a Transaction? + +Transactions are a Sentry-specific unit of measurement that references any event that users send to Sentry. In addition to standard event fields, transactions also contains child spans and have a unique transaction ID. From d6e91b50fd4ab1f1bad9615372bc67cc343521cc Mon Sep 17 00:00:00 2001 From: Liza Mock Date: Wed, 16 Oct 2024 14:39:39 -0700 Subject: [PATCH 2/4] update cta to get started --- src/components/header.tsx | 2 +- src/components/mobileMenu/index.tsx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/components/header.tsx b/src/components/header.tsx index c5c7f93d68316..70ef8f76c0a2a 100644 --- a/src/components/header.tsx +++ b/src/components/header.tsx @@ -73,7 +73,7 @@ export function Header({pathname, searchPlatforms, noSearch}: Props) { href="https://sentry.io/signup/" className="transition-all duration-300 ease-in-out hover:bg-gradient-to-r hover:from-[#fa7faa] hover:via-[#ff9691] hover:to-[#ffb287]" > - Start For Free + Get Started diff --git a/src/components/mobileMenu/index.tsx b/src/components/mobileMenu/index.tsx index dcb98294e627c..4cfc11ab16cf9 100644 --- a/src/components/mobileMenu/index.tsx +++ b/src/components/mobileMenu/index.tsx @@ -62,7 +62,7 @@ export function MobileMenu({pathname, searchPlatforms}: Props) { Sign In - Start For Free + Get Started From a47fce9e7f81ec96f5e9fc67a1695754b227c2b1 Mon Sep 17 00:00:00 2001 From: Liza Mock Date: Wed, 16 Oct 2024 15:37:59 -0700 Subject: [PATCH 3/4] Update docs/product/tracing/index.mdx --- docs/product/tracing/index.mdx | 24 ------------------------ 1 file changed, 24 deletions(-) diff --git a/docs/product/tracing/index.mdx b/docs/product/tracing/index.mdx index 2e6fda2b4ca55..cd21505a47e53 100644 --- a/docs/product/tracing/index.mdx +++ b/docs/product/tracing/index.mdx @@ -1,26 +1,2 @@ --- -title: Tracing -sidebar_order: 20 -description: "Learn about using tracing and distributed tracing for observing and debugging application performance issues. You'll see the impact of errors across your full stack and microservices." ---- - -## Tracing - -Tracing is the process of capturing the timing and flow of requests and operations as they happen throughout your application. It can be a powerful debugging tool, helping you identify which link in a sequence of events is causing a problem. - -### What's Distributed Tracing? - -Distributed tracing provides a unified view of how a single request moves from the frontend to the backend and beyond. This is particularly useful in modern applications, which are often composed of multiple services working together. To get a distributed view of your application, instrument Sentry in both your frontend and your backend. - -With distributed tracing, you can identify performance bottlenecks that are affecting your application no matter where in your application's workflowthey occur. You can then use Sentry tools such as the Trace Explorer or Trace View page to dig deeper and find the root cause of the problem. Distributed tracing is particularly helpful for identifying problems you can't just debug using console logs, such as race conditions, N+1, and caching issues. - -### What's a Trace? - -Each trace has a string of globally unique characters called a trace ID, that's shared by both frontend and backend services they help connect all the actions that take place to make an event such as a button click or a page scroll. Each trace is composed of multiple spans. - -### What's a Span? -A span is a named, timed operation that represents a part of the application workflow. It provides granular insights into specific tasks, like API requests or database queries. Multiple spans are pieced together to create a trace. providing a comprehensive view of its path, timing, and interactions for troubleshooting and performance analysis. - -### What's a Transaction? -Transactions are a Sentry-specific unit of measurement that references any event that users send to Sentry. In addition to standard event fields, transactions also contains child spans and have a unique transaction ID. From 1283c4f7ffa2f7d5f188eb98d6eafdabb57d3824 Mon Sep 17 00:00:00 2001 From: Liza Mock Date: Wed, 16 Oct 2024 15:38:41 -0700 Subject: [PATCH 4/4] Delete docs/product/tracing/index.mdx --- docs/product/tracing/index.mdx | 2 -- 1 file changed, 2 deletions(-) delete mode 100644 docs/product/tracing/index.mdx diff --git a/docs/product/tracing/index.mdx b/docs/product/tracing/index.mdx deleted file mode 100644 index cd21505a47e53..0000000000000 --- a/docs/product/tracing/index.mdx +++ /dev/null @@ -1,2 +0,0 @@ ---- -