diff --git a/docs/guides/custom-spans.mdx b/docs/guides/custom-spans.mdx index 48354999a20b0..528a89665e91a 100644 --- a/docs/guides/custom-spans.mdx +++ b/docs/guides/custom-spans.mdx @@ -6,7 +6,7 @@ description: "Add custom instrumentation for visibility beyond auto-instrumentat You've got your Sentry SDK [auto-instrumentation](/product/explore/trace-explorer/) running. Now what? -Auto-instrumentation captures HTTP, database, and framework operations. But it can't see business logic, third-party APIs without auto-instrumentation, or background jobs. This guide shows you where to add custom spans to fill in those gaps. +Auto-instrumentation captures HTTP, database, and framework operations. But it can't see business logic, third-party APIs without auto-instrumentation, or background jobs. This guide shows you where to add custom spans to fill in those gaps. The custom spans in this guide add business context, logical groupings, and attributes that auto-instrumentation can't provide. In many cases, your custom spans will appear as parents of auto-generated child spans. ## Anatomy of a Span diff --git a/docs/guides/issues-errors.mdx b/docs/guides/issues-errors.mdx index 3a85840517e1b..04a06d50c0607 100644 --- a/docs/guides/issues-errors.mdx +++ b/docs/guides/issues-errors.mdx @@ -4,7 +4,9 @@ sidebar_order: 5 description: "Practical guidance on what errors to catch, how to search issues, and when to set alerts." --- -Your Sentry SDK is sending errors to [Sentry Issues](/product/issues/) out of the box. Now what? This guide covers the high-value error patterns that help you catch problems before they impact users and fix issues faster. +Your Sentry SDK is sending errors to [Sentry Issues](/product/issues/) out of the box. Now what? + +This guide covers the high-value error patterns that help you catch problems before they impact users and fix issues faster. ## Anatomy of an Error diff --git a/docs/guides/logs.mdx b/docs/guides/logs.mdx index 74c49b061f904..77f98554c6fa3 100644 --- a/docs/guides/logs.mdx +++ b/docs/guides/logs.mdx @@ -4,7 +4,9 @@ sidebar_order: 10 description: "Practical guidance on what to log, how to search logs, and when to set alerts." --- -You've set up [Sentry Logs](/product/explore/logs/). Now what? This guide covers the high-value logging patterns that help you debug faster and catch problems before users report them. +You've set up [Sentry Logs](/product/explore/logs/). Now what? + +This guide covers the high-value logging patterns that help you debug faster and catch problems before users report them. ## Anatomy of a Log diff --git a/docs/guides/metrics.mdx b/docs/guides/metrics.mdx index 754ea20ba8b04..06c2daf41aea7 100644 --- a/docs/guides/metrics.mdx +++ b/docs/guides/metrics.mdx @@ -4,7 +4,9 @@ sidebar_order: 15 description: "Practical guidance on what metrics to track, how to explore them, and when to set alerts." --- -You've set up [Sentry Metrics](/product/explore/metrics/). Now what? This guide covers the high-value metric patterns that give you visibility into application health and how to drill into traces when something looks off. +You've set up [Sentry Metrics](/product/explore/metrics/). Now what? + +This guide covers the high-value metric patterns that give you visibility into application health and how to drill into traces when something looks off. ## Anatomy of a Metric diff --git a/docs/guides/querying-traces.mdx b/docs/guides/querying-traces.mdx index 27b7863a66cfc..f0b37b13a595b 100644 --- a/docs/guides/querying-traces.mdx +++ b/docs/guides/querying-traces.mdx @@ -4,7 +4,9 @@ sidebar_order: 20 description: "Find performance issues using data Sentry captures automatically and set up alerts." --- -You've enabled [Sentry Tracing](/product/explore/trace-explorer/). Now what? Sentry's auto-instrumentation captures a lot without custom code. This guide shows you how to query that data to find performance issues. +You've enabled [Sentry Tracing](/product/explore/trace-explorer/). Now what? + +Sentry's auto-instrumentation captures a lot without custom code. This guide shows you how to query that data to find performance issues. diff --git a/docs/guides/session-replay.mdx b/docs/guides/session-replay.mdx index 4484e714bb43b..c77ad2286370b 100644 --- a/docs/guides/session-replay.mdx +++ b/docs/guides/session-replay.mdx @@ -4,7 +4,9 @@ sidebar_order: 40 description: "Practical guidance on debugging errors and finding UX issues with Session Replay." --- -You've set up [Sentry Session Replay](/product/explore/session-replay/). Now what? Stack traces tell you _what_ broke. Replay shows you _how_ it broke. This guide covers how to use replay to debug errors and spot UX problems before users report them. +You've set up [Sentry Session Replay](/product/explore/session-replay/). Now what? + +Stack traces tell you _what_ broke. Replay shows you _how_ it broke. This guide covers how to use replay to debug errors and spot UX problems before users report them. ## What Replay Captures