From 574d6585bffbded1c54331a0755b841dbf6a2d03 Mon Sep 17 00:00:00 2001 From: Shannon Anahata Date: Wed, 6 May 2026 16:41:29 -0700 Subject: [PATCH 1/6] Deleted /product/insights, redirecting all to /product/dashboards/sentry-dashboards, updated links across repo. Co-authored-by: Cursor --- .github/CODEOWNERS | 2 +- .../sentry-vs-getsentry.mdx | 2 +- .../transaction-clustering/index.mdx | 2 +- .../sdk/telemetry/traces/opentelemetry.mdx | 2 +- .../optional-features/errors-only.mdx | 4 +- docs/concepts/key-terms/key-terms.mdx | 2 +- .../key-terms/tracing/distributed-tracing.mdx | 6 +- docs/concepts/key-terms/tracing/index.mdx | 4 +- docs/concepts/search/index.mdx | 2 +- .../search/searchable-properties/events.mdx | 26 +-- .../search/searchable-properties/issues.mdx | 2 +- .../approach/product-docs/write-index.mdx | 2 +- docs/guides/custom-spans.mdx | 2 +- .../transaction-name/index.mdx | 2 +- docs/platforms/android/features/index.mdx | 2 +- docs/platforms/android/overhead/index.mdx | 2 +- docs/platforms/android/tracing/index.mdx | 2 +- .../automatic-instrumentation.mdx | 4 +- .../tracing/instrumentation/perf-v2.mdx | 2 +- .../platforms/apple/common/features/index.mdx | 2 +- .../platforms/apple/common/overhead/index.mdx | 2 +- docs/platforms/apple/common/tracing/index.mdx | 2 +- .../automatic-instrumentation.mdx | 4 +- .../swiftui-instrumentation.mdx | 2 +- .../apple/guides/ios/features/index.mdx | 2 +- .../apple/guides/macos/features/index.mdx | 2 +- .../apple/guides/tvos/features/index.mdx | 2 +- .../apple/guides/visionos/features/index.mdx | 2 +- .../transaction-name/index.mdx | 2 +- docs/platforms/dart/common/features/index.mdx | 2 +- docs/platforms/dart/common/overhead/index.mdx | 2 +- docs/platforms/dart/common/tracing/index.mdx | 2 +- .../guides/flutter/configuration/options.mdx | 2 +- .../transaction-name/index.mdx | 2 +- .../dart/guides/flutter/overhead/index.mdx | 2 +- .../dart/guides/flutter/tracing/index.mdx | 2 +- .../automatic-instrumentation.mdx | 2 +- .../transaction-name/index.mdx | 2 +- .../platforms/dotnet/common/tracing/index.mdx | 2 +- docs/platforms/elixir/tracing/index.mdx | 2 +- .../transaction-name/index.mdx | 2 +- docs/platforms/go/common/tracing/index.mdx | 2 +- .../transaction-name/index.mdx | 2 +- docs/platforms/java/common/tracing/index.mdx | 2 +- .../integrations/browsertracing.mdx | 2 +- .../configuration/integrations/supabase.mdx | 2 +- .../javascript/common/tracing/index.mdx | 2 +- .../automatic-instrumentation.mdx | 2 +- .../instrumentation/requests-module.mdx | 2 +- .../guides/nextjs/tracing/index.mdx | 4 +- .../transaction-name/index.mdx | 2 +- .../platforms/native/common/tracing/index.mdx | 2 +- docs/platforms/php/common/tracing/index.mdx | 2 +- docs/platforms/powershell/tracing/index.mdx | 2 +- .../transaction-name/index.mdx | 2 +- .../requests-module.mdx | 2 +- .../python/tracing/span-lifecycle/index.mdx | 2 +- .../react-native/configuration/options.mdx | 2 +- .../transaction-name/index.mdx | 2 +- .../platforms/react-native/features/index.mdx | 2 +- .../platforms/react-native/overhead/index.mdx | 2 +- docs/platforms/react-native/tracing/index.mdx | 2 +- .../automatic-instrumentation.mdx | 6 +- .../instrumentation/time-to-display.mdx | 2 +- .../transaction-name/index.mdx | 2 +- docs/platforms/ruby/common/migration.mdx | 2 +- docs/platforms/ruby/common/tracing/index.mdx | 2 +- .../requests-module.mdx | 2 +- docs/platforms/rust/common/tracing/index.mdx | 2 +- .../transaction-name/index.mdx | 2 +- docs/platforms/unity/tracing/index.mdx | 2 +- docs/platforms/unreal/tracing/index.mdx | 2 +- docs/pricing/legacy-pricing.mdx | 2 +- .../dashboards/sentry-dashboards/nextjs.mdx | 2 +- .../explore/profiling/getting-started.mdx | 2 +- .../mobile-app-profiling/metrics.mdx | 2 +- .../explore/session-replay/replay-details.mdx | 2 +- .../explore/session-replay/web/index.mdx | 2 +- .../insights/backend/caches/cache-page.mdx | 35 ---- .../product/insights/backend/caches/index.mdx | 38 ---- docs/product/insights/backend/index.mdx | 24 --- docs/product/insights/backend/queries.mdx | 134 ------------- .../backend/queue-monitoring/index.mdx | 34 ---- .../backend/queue-monitoring/queues-page.mdx | 54 ------ docs/product/insights/backend/requests.mdx | 13 -- docs/product/insights/frontend/assets.mdx | 166 ---------------- docs/product/insights/frontend/index.mdx | 24 --- .../insights/frontend/network-requests.mdx | 13 -- .../insights/frontend/session-health.mdx | 15 -- .../insights/frontend/web-vitals/index.mdx | 105 ----------- .../web-vitals/web-vitals-concepts.mdx | 119 ------------ docs/product/insights/getting-started.mdx | 106 ----------- .../insights/img/asset-sample-images.png | Bin 173261 -> 0 bytes .../img/backend-performance-overview.png | Bin 102493 -> 0 bytes .../insights/img/diagram-transaction-cls.png | Bin 494145 -> 0 bytes .../img/diagram-transaction-vitals.png | Bin 404597 -> 0 bytes .../img/frontend-performance-overview.png | Bin 125149 -> 0 bytes .../img/mobile-performance-overview.png | Bin 153468 -> 0 bytes .../insights/img/query-source-laravel.png | Bin 22393 -> 0 bytes docs/product/insights/index.mdx | 17 -- docs/product/insights/mobile/index.mdx | 22 --- .../mobile/mobile-vitals/app-starts.mdx | 103 ---------- .../img/01_full_widget_mobile.png | Bin 251892 -> 0 bytes .../img/app-start-transaction.png | Bin 322194 -> 0 bytes .../img/app-starts-samples-by-event.png | Bin 41803 -> 0 bytes .../img/app-starts-span-detail-view.png | Bin 314278 -> 0 bytes .../mobile/mobile-vitals/img/app-starts.png | Bin 107026 -> 0 bytes .../mobile-vitals/img/mobile-vitals.png | Bin 85707 -> 0 bytes .../img/screen-loads-span-detail.png | Bin 334930 -> 0 bytes .../mobile/mobile-vitals/img/screen-loads.png | Bin 129178 -> 0 bytes .../mobile-vitals/img/slow-frozen-frames.png | Bin 235248 -> 0 bytes .../img/time-to-initial-full-display.png | Bin 266872 -> 0 bytes .../img/ttid-ttfd-affecting-spans.png | Bin 66966 -> 0 bytes .../insights/mobile/mobile-vitals/index.mdx | 112 ----------- .../mobile/mobile-vitals/screen-loads.mdx | 94 ---------- .../insights/mobile/network-requests.mdx | 13 -- .../insights/mobile/session-health.mdx | 15 -- .../img/01_half_widget_frontend.png | Bin 168253 -> 0 bytes .../img/transaction-name-search.png | Bin 8248 -> 0 bytes .../img/widgets_average_ttids.png | Bin 164285 -> 0 bytes .../img/widgets_best_page_opportunities.png | Bin 168355 -> 0 bytes .../img/widgets_most_frozen_frames.png | Bin 180368 -> 0 bytes .../img/widgets_most_related_issues.png | Bin 179427 -> 0 bytes .../img/widgets_most_slow_frames.png | Bin 177997 -> 0 bytes .../widgets_most_time_consuming_domains.png | Bin 350292 -> 0 bytes .../img/widgets_most_time_spent_assets.png | Bin 190965 -> 0 bytes .../img/widgets_most_time_spent_queries.png | Bin 185352 -> 0 bytes .../img/widgets_performance_score.png | Bin 155180 -> 0 bytes .../img/widgets_slow_db_ops.png | Bin 161354 -> 0 bytes .../img/widgets_slow_http_ops.png | Bin 177781 -> 0 bytes .../img/widgets_slow_resource_ops.png | Bin 170796 -> 0 bytes .../overview/filters-display/index.mdx | 113 ----------- .../overview/filters-display/widgets.mdx | 104 ---------- .../overview/img/01_full_widget_all.png | Bin 150960 -> 0 bytes .../img/custom-metrics-performance.png | Bin 342374 -> 0 bytes .../insights/overview/img/exclusive-time.png | Bin 19180 -> 0 bytes .../overview/img/perf-transaction-summary.png | Bin 178664 -> 0 bytes .../overview/img/resource-sample-images.png | Bin 126885 -> 0 bytes .../insights/overview/img/tags-tab.png | Bin 210077 -> 0 bytes .../overview/img/transaction-trace-detail.png | Bin 178412 -> 0 bytes docs/product/insights/overview/img/trends.png | Bin 129455 -> 0 bytes docs/product/insights/overview/index.mdx | 63 ------- docs/product/insights/overview/metrics.mdx | 134 ------------- .../insights/overview/transaction-summary.mdx | 177 ------------------ .../product/insights/performance-overhead.mdx | 55 ------ .../endpoint-regressions/index.mdx | 2 +- .../performance-issues/index.mdx | 2 +- .../large-render-blocking-asset/index.mdx | 2 +- .../performance-issues/web-vitals/index.mdx | 6 +- .../integrate-frontend/configure-scms.mdx | 2 +- .../sentry-basics/performance-monitoring.mdx | 8 +- includes/docs-changelog.mdx | 6 +- middleware.ts | 88 ++++----- .../getting-started-primer/dotnet.mdx | 2 +- .../browser-profiling/javascript.mdx | 2 +- redirects.js | 84 +++++---- 156 files changed, 207 insertions(+), 2097 deletions(-) delete mode 100644 docs/product/insights/backend/caches/cache-page.mdx delete mode 100644 docs/product/insights/backend/caches/index.mdx delete mode 100644 docs/product/insights/backend/index.mdx delete mode 100644 docs/product/insights/backend/queries.mdx delete mode 100644 docs/product/insights/backend/queue-monitoring/index.mdx delete mode 100644 docs/product/insights/backend/queue-monitoring/queues-page.mdx delete mode 100644 docs/product/insights/backend/requests.mdx delete mode 100644 docs/product/insights/frontend/assets.mdx delete mode 100644 docs/product/insights/frontend/index.mdx delete mode 100644 docs/product/insights/frontend/network-requests.mdx delete mode 100644 docs/product/insights/frontend/session-health.mdx delete mode 100644 docs/product/insights/frontend/web-vitals/index.mdx delete mode 100644 docs/product/insights/frontend/web-vitals/web-vitals-concepts.mdx delete mode 100644 docs/product/insights/getting-started.mdx delete mode 100644 docs/product/insights/img/asset-sample-images.png delete mode 100644 docs/product/insights/img/backend-performance-overview.png delete mode 100644 docs/product/insights/img/diagram-transaction-cls.png delete mode 100644 docs/product/insights/img/diagram-transaction-vitals.png delete mode 100644 docs/product/insights/img/frontend-performance-overview.png delete mode 100644 docs/product/insights/img/mobile-performance-overview.png delete mode 100644 docs/product/insights/img/query-source-laravel.png delete mode 100644 docs/product/insights/index.mdx delete mode 100644 docs/product/insights/mobile/index.mdx delete mode 100644 docs/product/insights/mobile/mobile-vitals/app-starts.mdx delete mode 100644 docs/product/insights/mobile/mobile-vitals/img/01_full_widget_mobile.png delete mode 100644 docs/product/insights/mobile/mobile-vitals/img/app-start-transaction.png delete mode 100644 docs/product/insights/mobile/mobile-vitals/img/app-starts-samples-by-event.png delete mode 100644 docs/product/insights/mobile/mobile-vitals/img/app-starts-span-detail-view.png delete mode 100644 docs/product/insights/mobile/mobile-vitals/img/app-starts.png delete mode 100644 docs/product/insights/mobile/mobile-vitals/img/mobile-vitals.png delete mode 100644 docs/product/insights/mobile/mobile-vitals/img/screen-loads-span-detail.png delete mode 100644 docs/product/insights/mobile/mobile-vitals/img/screen-loads.png delete mode 100644 docs/product/insights/mobile/mobile-vitals/img/slow-frozen-frames.png delete mode 100644 docs/product/insights/mobile/mobile-vitals/img/time-to-initial-full-display.png delete mode 100644 docs/product/insights/mobile/mobile-vitals/img/ttid-ttfd-affecting-spans.png delete mode 100644 docs/product/insights/mobile/mobile-vitals/index.mdx delete mode 100644 docs/product/insights/mobile/mobile-vitals/screen-loads.mdx delete mode 100644 docs/product/insights/mobile/network-requests.mdx delete mode 100644 docs/product/insights/mobile/session-health.mdx delete mode 100644 docs/product/insights/overview/filters-display/img/01_half_widget_frontend.png delete mode 100644 docs/product/insights/overview/filters-display/img/transaction-name-search.png delete mode 100644 docs/product/insights/overview/filters-display/img/widgets_average_ttids.png delete mode 100644 docs/product/insights/overview/filters-display/img/widgets_best_page_opportunities.png delete mode 100644 docs/product/insights/overview/filters-display/img/widgets_most_frozen_frames.png delete mode 100644 docs/product/insights/overview/filters-display/img/widgets_most_related_issues.png delete mode 100644 docs/product/insights/overview/filters-display/img/widgets_most_slow_frames.png delete mode 100644 docs/product/insights/overview/filters-display/img/widgets_most_time_consuming_domains.png delete mode 100644 docs/product/insights/overview/filters-display/img/widgets_most_time_spent_assets.png delete mode 100644 docs/product/insights/overview/filters-display/img/widgets_most_time_spent_queries.png delete mode 100644 docs/product/insights/overview/filters-display/img/widgets_performance_score.png delete mode 100644 docs/product/insights/overview/filters-display/img/widgets_slow_db_ops.png delete mode 100644 docs/product/insights/overview/filters-display/img/widgets_slow_http_ops.png delete mode 100644 docs/product/insights/overview/filters-display/img/widgets_slow_resource_ops.png delete mode 100644 docs/product/insights/overview/filters-display/index.mdx delete mode 100644 docs/product/insights/overview/filters-display/widgets.mdx delete mode 100644 docs/product/insights/overview/img/01_full_widget_all.png delete mode 100644 docs/product/insights/overview/img/custom-metrics-performance.png delete mode 100644 docs/product/insights/overview/img/exclusive-time.png delete mode 100644 docs/product/insights/overview/img/perf-transaction-summary.png delete mode 100644 docs/product/insights/overview/img/resource-sample-images.png delete mode 100644 docs/product/insights/overview/img/tags-tab.png delete mode 100644 docs/product/insights/overview/img/transaction-trace-detail.png delete mode 100644 docs/product/insights/overview/img/trends.png delete mode 100644 docs/product/insights/overview/index.mdx delete mode 100644 docs/product/insights/overview/metrics.mdx delete mode 100644 docs/product/insights/overview/transaction-summary.mdx delete mode 100644 docs/product/insights/performance-overhead.mdx diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS index 5e7d0fd4f9cb7..8d90f2bbbfb46 100644 --- a/.github/CODEOWNERS +++ b/.github/CODEOWNERS @@ -27,7 +27,7 @@ # /docs/platforms/rust/ @getsentry/team-web-sdk-backend # /docs/product/explore/discover-queries/ @getsentry/data-browsing -# /docs/product/insights/ @getsentry/dashboards +# /docs/product/dashboards/sentry-dashboards/ @getsentry/dashboards # /docs/cli/ @getsentry/team-web-sdk-backend diff --git a/develop-docs/application-architecture/sentry-vs-getsentry.mdx b/develop-docs/application-architecture/sentry-vs-getsentry.mdx index a4bd187193fe7..bff019354597a 100644 --- a/develop-docs/application-architecture/sentry-vs-getsentry.mdx +++ b/develop-docs/application-architecture/sentry-vs-getsentry.mdx @@ -5,7 +5,7 @@ sidebar_order: 20 You'll find numerous references to both `sentry` and `getsentry` in our documentation. Both are [Django](https://www.djangoproject.com/) apps, but `sentry` [is open](https://github.com/getsentry/sentry) and `getsentry` is closed. What's in which? -The main thing to emphasize is that all of our product features—[Issues](https://docs.sentry.io/product/issues/), [Insights](https://docs.sentry.io/product/insights/), [Dashboards](https://docs.sentry.io/product/dashboards/), and [such](https://docs.sentry.io/product/)—are implemented and available in `sentry`, the open component. It's really important to us that we're not an "open core" company that hides key functionality behind a paywall. [Sentry is as open-source as we can make it](https://open.sentry.io/licensing/). +The main thing to emphasize is that all of our product features—[Issues](https://docs.sentry.io/product/issues/), [Insights](https://docs.sentry.io/product/dashboards/sentry-dashboards/), [Dashboards](https://docs.sentry.io/product/dashboards/), and [such](https://docs.sentry.io/product/)—are implemented and available in `sentry`, the open component. It's really important to us that we're not an "open core" company that hides key functionality behind a paywall. [Sentry is as open-source as we can make it](https://open.sentry.io/licensing/). So what's in `getsentry`, then? It implements billing and account management features for [our SaaS, sentry.io](https://sentry.io/). `getsentry` is the Django app we deploy to production. It imports the `sentry` Django app, adds some routes and models, and re-exports it. diff --git a/develop-docs/backend/application-domains/transaction-clustering/index.mdx b/develop-docs/backend/application-domains/transaction-clustering/index.mdx index bcfcb49262826..0bcb5a9728734 100644 --- a/develop-docs/backend/application-domains/transaction-clustering/index.mdx +++ b/develop-docs/backend/application-domains/transaction-clustering/index.mdx @@ -12,7 +12,7 @@ In terms of technical implementation, it is similar to [Data Scrubbing](/backend ## The Problem -In our [Insights](https://docs.sentry.io/product/insights/overview/) product, transactions are grouped by their name +In our [Insights](https://docs.sentry.io/product/dashboards/sentry-dashboards/) product, transactions are grouped by their name (the [`event.transaction`](/sdk/foundations/transport/event-payloads/#optional-attributes) field). This works well as long as the cardinality of distinct transaction names that the SDK sends is low, for example by using the [route of a web framework](https://docs.sentry.io/platforms/javascript/guides/react/configuration/integrations/react-router/) as the transaction name. diff --git a/develop-docs/sdk/telemetry/traces/opentelemetry.mdx b/develop-docs/sdk/telemetry/traces/opentelemetry.mdx index 182b950475416..62b90b031edf4 100644 --- a/develop-docs/sdk/telemetry/traces/opentelemetry.mdx +++ b/develop-docs/sdk/telemetry/traces/opentelemetry.mdx @@ -10,7 +10,7 @@ This page is under active development. Specifications are not final and subject -This document details Sentry's work in integrating and supporting [OpenTelemetry](https://opentelemetry.io/), the open standard for metrics, traces and logs. In particular, it focuses on the integration between [Sentry's performance monitoring product](https://docs.sentry.io/product/insights/overview/) and [OpenTelemetry's tracing spec](https://opentelemetry.io/docs/concepts/signals/traces/). +This document details Sentry's work in integrating and supporting [OpenTelemetry](https://opentelemetry.io/), the open standard for metrics, traces and logs. In particular, it focuses on the integration between [Sentry's performance monitoring product](https://docs.sentry.io/product/dashboards/sentry-dashboards/) and [OpenTelemetry's tracing spec](https://opentelemetry.io/docs/concepts/signals/traces/). ## Background diff --git a/develop-docs/self-hosted/optional-features/errors-only.mdx b/develop-docs/self-hosted/optional-features/errors-only.mdx index b249ce6708066..1f093a95e7f8a 100644 --- a/develop-docs/self-hosted/optional-features/errors-only.mdx +++ b/develop-docs/self-hosted/optional-features/errors-only.mdx @@ -24,9 +24,9 @@ This is our default version of self-hosted Sentry. It includes most of the featu 1. [Traces](https://docs.sentry.io/product/explore/traces/) 2. [Profiles](https://docs.sentry.io/product/explore/profiling/) 3. [Replays](https://docs.sentry.io/product/explore/session-replay/) -4. [Insights](https://docs.sentry.io/product/insights/) (Requests, Queries, Assets, etc) +4. [Insights](https://docs.sentry.io/product/dashboards/sentry-dashboards/) (Requests, Queries, Assets, etc) 5. [User Feedback](https://docs.sentry.io/product/user-feedback/) -6. [Insights](https://docs.sentry.io/product/insights/) +6. [Insights](https://docs.sentry.io/product/dashboards/sentry-dashboards/) 7. [Crons](https://docs.sentry.io/product/monitors-and-alerts/monitors/crons/) 8. [Application Metrics](https://docs.sentry.io/product/explore/metrics/) diff --git a/docs/concepts/key-terms/key-terms.mdx b/docs/concepts/key-terms/key-terms.mdx index 83318c70505ee..896d16872afe4 100644 --- a/docs/concepts/key-terms/key-terms.mdx +++ b/docs/concepts/key-terms/key-terms.mdx @@ -58,7 +58,7 @@ Each of these key features have their own page (or set of pages) in the [sentry. - **Insights** - Sentry surfaces insights that can help you identify opportunities at the service-level to improve various parts of your app's performance, including requests, assets, caches, queues, and more. Modules living under the Insights heading provide an overview of how your project is performing in that category, as well as the ability to review sample events and their traces to help you diagnose potential problems. -- **Insights Overview** - The main view in [sentry.io](http://sentry.io) where you can search or browse for transaction data. The page displays graphs that visualize transactions or trends, as well as a table where you can view relevant transactions and drill down to more information about them. Learn more in the full [performance monitoring documentation](/product/insights/overview/). +- **Insights Overview** - The main view in [sentry.io](http://sentry.io) where you can search or browse for transaction data. The page displays graphs that visualize transactions or trends, as well as a table where you can view relevant transactions and drill down to more information about them. Learn more in the full [performance monitoring documentation](/product/dashboards/sentry-dashboards/). - **Alerts** - Where you can create new alert rules and manage existing ones. Learn more in the full [Alerts documentation](/product/monitors-and-alerts/alerts/). diff --git a/docs/concepts/key-terms/tracing/distributed-tracing.mdx b/docs/concepts/key-terms/tracing/distributed-tracing.mdx index 72dc49d785fbd..138a0c6a2a456 100644 --- a/docs/concepts/key-terms/tracing/distributed-tracing.mdx +++ b/docs/concepts/key-terms/tracing/distributed-tracing.mdx @@ -8,7 +8,7 @@ description: >- og_image: /og-images/concepts-key-terms-tracing-distributed-tracing.png --- -Distributed tracing provides a connected view of your application from frontend to backend. It helps track software performance, measure [metrics](/product/dashboards/sentry-dashboards/transaction-summary/#metrics-in-this-view) like throughput and latency, and display the impact of errors across multiple systems. This makes Sentry a more complete [performance monitoring](/product/insights/overview/) solution, aiding in diagnosing problems and measuring your application's overall health. +Distributed tracing provides a connected view of your application from frontend to backend. It helps track software performance, measure [metrics](/product/dashboards/sentry-dashboards/transaction-summary/#metrics-in-this-view) like throughput and latency, and display the impact of errors across multiple systems. This makes Sentry a more complete [performance monitoring](/product/dashboards/sentry-dashboards/) solution, aiding in diagnosing problems and measuring your application's overall health. [Tracing](/concepts/key-terms/tracing/distributed-tracing/) in Sentry provides insights such as: @@ -80,7 +80,7 @@ Distributed tracing allows you to follow a request from the [frontend](/product/ A **trace** represents the record of the entire operation you want to measure or track, like page load or a user action. When a trace includes work in multiple services, it's called a **distributed trace**. -Each trace consists of one or more tree-like structures called [**transactions**](/product/insights/overview/transaction-summary/), with nodes called **spans**. Each transaction represents a single instance of a service being called, and each span represents a single unit of work. Here's an example trace, broken down into transactions and spans: +Each trace consists of one or more tree-like structures called [**transactions**](/product/dashboards/sentry-dashboards/transaction-summary/), with nodes called **spans**. Each transaction represents a single instance of a service being called, and each span represents a single unit of work. Here's an example trace, broken down into transactions and spans: ![Diagram illustrating how a trace is composed of multiple transactions, and each transaction is composed of multiple spans.](./img/diagram-transaction-trace.png) @@ -231,4 +231,4 @@ Dynamic sampling ensures complete traces by retaining all transactions associate Use the [Trace Explorer](/product/explore/traces/) to search for traces containing spans that meet your specific query conditions. This helps you find distributed traces that give you a connected view of your application and can help you debug and optimize your code. -Through [Performance](/product/insights/overview/) and [Discover](/product/explore/discover-queries/), you can also view trace data in the [Trace View](/concepts/key-terms/tracing/trace-view/) page. +Through [Performance](/product/dashboards/sentry-dashboards/) and [Discover](/product/explore/discover-queries/), you can also view trace data in the [Trace View](/concepts/key-terms/tracing/trace-view/) page. diff --git a/docs/concepts/key-terms/tracing/index.mdx b/docs/concepts/key-terms/tracing/index.mdx index 075211d5ab1c4..efea47cc814c2 100644 --- a/docs/concepts/key-terms/tracing/index.mdx +++ b/docs/concepts/key-terms/tracing/index.mdx @@ -17,7 +17,7 @@ Tracing involves capturing the timing and flow of requests and operations as the 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 separate services working together. To get a distributed view of your application, instrument Sentry in both your frontend and your backend. -With [distributed tracing](/concepts/key-terms/tracing/distributed-tracing/), you can identify performance bottlenecks that are affecting your application across different services and platforms. You can then use Sentry tools such as the [Trace Explorer](/product/explore/traces/) or [Trace View](/concepts/key-terms/tracing/trace-view/) page to dig deeper and find the root cause of the problem. Distributed tracing is particularly helpful for identifying problems that take place between multiple services that you can't debug using console logs, such as race conditions, [N+1 queries](/product/issues/issue-details/performance-issues/n-one-queries/), and [caching issues](/product/insights/caches/). +With [distributed tracing](/concepts/key-terms/tracing/distributed-tracing/), you can identify performance bottlenecks that are affecting your application across different services and platforms. You can then use Sentry tools such as the [Trace Explorer](/product/explore/traces/) or [Trace View](/concepts/key-terms/tracing/trace-view/) page to dig deeper and find the root cause of the problem. Distributed tracing is particularly helpful for identifying problems that take place between multiple services that you can't debug using console logs, such as race conditions, [N+1 queries](/product/issues/issue-details/performance-issues/n-one-queries/), and [caching issues](/product/dashboards/sentry-dashboards/backend/caches/). ### What's a Trace? @@ -55,7 +55,7 @@ Alternatively, you can use the search bar to look for spans by name, project, or ### Performance to Trace View -Depending on the size and volume of your app, you may have a lot of traces to sort through. The [Insights](https://sentry.io/orgredirect/organizations/:orgslug/insights/backend/) page in Sentry is a good place to get a high-level, aggregated view of your application's performance and focus in on the traces you care about. You'll see a list of transactions for specific pages, endpoints and parts of your application. Clicking on the transaction ID will take you to the Trace View page for that transaction. Learn more about using Sentry's [Insights](/product/insights/). +Depending on the size and volume of your app, you may have a lot of traces to sort through. The [Sentry Dashboards](https://sentry.io/orgredirect/organizations/:orgslug/insights/backend/) page in Sentry is a good place to get a high-level, aggregated view of your application's performance and focus in on the traces you care about. You'll see a list of transactions for specific pages, endpoints and parts of your application. Clicking on the transaction ID will take you to the Trace View page for that transaction. Learn more about using [Sentry Dashboards](/product/dashboards/sentry-dashboards/). ![An overview of the Performance page in Sentry.](./img/Performance-page.png) diff --git a/docs/concepts/search/index.mdx b/docs/concepts/search/index.mdx index 16ca7db28b1cd..7ce694d68a388 100644 --- a/docs/concepts/search/index.mdx +++ b/docs/concepts/search/index.mdx @@ -60,7 +60,7 @@ Here are some examples of valid comparison operator searches: -`OR` and `AND` search conditions are only available for [Discover](/product/explore/discover-queries/), [Insights Overview](/product/insights/overview/), and [Monitors](/product/monitors-and-alerts/monitors/). +`OR` and `AND` search conditions are only available for [Discover](/product/explore/discover-queries/), [Sentry Dashboards](/product/dashboards/sentry-dashboards/), and [Monitors](/product/monitors-and-alerts/monitors/). diff --git a/docs/concepts/search/searchable-properties/events.mdx b/docs/concepts/search/searchable-properties/events.mdx index e91ccf07f254d..45679b4988fdb 100644 --- a/docs/concepts/search/searchable-properties/events.mdx +++ b/docs/concepts/search/searchable-properties/events.mdx @@ -30,7 +30,7 @@ Below is a list of keys and tokens that can be used in the event search. ### `apdex(threshold)` -Returns results with the [Apdex score](/product/insights/overview/metrics/#apdex) that you entered. Values must be between `0` and `1`. Higher apdex values indicate higher user satisfaction. +Returns results with the Apdex score that you entered. Values must be between `0` and `1`. Higher apdex values indicate higher user satisfaction. - **Type:** number @@ -342,43 +342,43 @@ Returns results with a matching maximum value for the field entered. ### `measurements.app_start_cold` -A [cold start](/product/insights/mobile/mobile-vitals/app-starts/) on Android refers to when the app process is created from scratch. On iOS it is only the first time a process is created after a reboot or update. +A [cold start](/product/dashboards/sentry-dashboards/mobile/mobile-vitals/app-starts/) on Android refers to when the app process is created from scratch. On iOS it is only the first time a process is created after a reboot or update. - **Type:** duration ### `measurements.app_start_warm` -A [warm start](/product/insights/mobile/mobile-vitals/app-starts/) on Android refers to when the app launches with some saved state, for example it may have an existing process and only need to create a new Activity. On iOS it is any process creation that isn't a cold start. +A [warm start](/product/dashboards/sentry-dashboards/mobile/mobile-vitals/app-starts/) on Android refers to when the app launches with some saved state, for example it may have an existing process and only need to create a new Activity. On iOS it is any process creation that isn't a cold start. - **Type:** duration ### `measurements.cls` -[Cumulative Layout Shift (CLS)](/product/insights/web-vitals/web-vitals-concepts/#cumulative-layout-shift-cls) is the sum of individual layout shift scores for every unexpected element shift during the rendering process. +[Cumulative Layout Shift (CLS)](/product/dashboards/sentry-dashboards/frontend/web-vitals/web-vitals-concepts/#cumulative-layout-shift-cls) is the sum of individual layout shift scores for every unexpected element shift during the rendering process. - **Type:** number ### `measurements.fcp` -[First Contentful Paint (FCP)](/product/insights/web-vitals/web-vitals-concepts/#first-contentful-paint-fcp) measures the time for the first content to render in the viewport. +[First Contentful Paint (FCP)](/product/dashboards/sentry-dashboards/frontend/web-vitals/web-vitals-concepts/#first-contentful-paint-fcp) measures the time for the first content to render in the viewport. - **Type:** duration ### `measurements.fid` -[First Input Delay (FID)](/product/insights/web-vitals/web-vitals-concepts/#first-input-delay-fid) measures the response time when the user tries to interact with the viewport. +[First Input Delay (FID)](/product/dashboards/sentry-dashboards/frontend/web-vitals/web-vitals-concepts/#first-input-delay-fid) measures the response time when the user tries to interact with the viewport. - **Type:** duration ### `measurements.fp` -[First Paint (FP)](/product/insights/web-vitals/web-vitals-concepts/#first-paint-fp) measures the amount of time the first pixel takes to appear in the viewport, rendering any visual change from what was previously displayed. +[First Paint (FP)](/product/dashboards/sentry-dashboards/frontend/web-vitals/web-vitals-concepts/#first-paint-fp) measures the amount of time the first pixel takes to appear in the viewport, rendering any visual change from what was previously displayed. - **Type:** duration ### `measurements.frames_frozen` -[Slow and frozen frames](/product/insights/mobile/mobile-vitals/#slow-and-frozen-frames) measure the responsiveness of your app. +[Slow and frozen frames](/product/dashboards/sentry-dashboards/mobile/mobile-vitals/#slow-and-frozen-frames) measure the responsiveness of your app. - **Type:** number @@ -390,7 +390,7 @@ Returns results with a matching rate of frozen frames. That is, `measurements.fr ### `measurements.frames_slow` -[Slow and frozen frames](/product/insights/mobile/mobile-vitals/#slow-and-frozen-frames) measure the responsiveness of your app. +[Slow and frozen frames](/product/dashboards/sentry-dashboards/mobile/mobile-vitals/#slow-and-frozen-frames) measure the responsiveness of your app. - **Type:** number @@ -408,7 +408,7 @@ Returns results with a matching total number of frames. ### `measurements.lcp` -[Largest Contentful Paint (LCP)](/product/insights/web-vitals/web-vitals-concepts/#largest-contentful-paint-lcp) measures the render time for the largest content to appear in the viewport. +[Largest Contentful Paint (LCP)](/product/dashboards/sentry-dashboards/frontend/web-vitals/web-vitals-concepts/#largest-contentful-paint-lcp) measures the render time for the largest content to appear in the viewport. - **Type:** duration @@ -438,7 +438,7 @@ The [total stall time](/platforms/react-native/tracing/instrumentation/automatic ### `measurements.ttfb` -[Time To First Byte (TTFB)](/product/insights/web-vitals/web-vitals-concepts/#time-to-first-byte-ttfb) measures the time that it takes for a user's browser to receive the first byte of page content. +[Time To First Byte (TTFB)](/product/dashboards/sentry-dashboards/frontend/web-vitals/web-vitals-concepts/#time-to-first-byte-ttfb) measures the time that it takes for a user's browser to receive the first byte of page content. - **Type:** duration @@ -685,7 +685,7 @@ Span ID of the root span of the root transaction in the event. ### `transaction` -For [transactions](/product/insights/overview/transaction-summary/#what-is-a-transaction), the name of the transaction. For errors, the name of the associated transaction. +For [transactions](/product/dashboards/sentry-dashboards/transaction-summary/#what-is-a-transaction), the name of the transaction. For errors, the name of the associated transaction. - **Type:** string @@ -715,7 +715,7 @@ The [Unreal Crash Context Type](https://docs.unrealengine.com/4.27/en-US/API/Run ### `user_misery(number)` -Returns transactions with the defined user misery value. [User Misery](/product/insights/overview/metrics/#user-misery) is a user-weighted performance metric that counts the number of unique users who were frustrated; "frustration" is measured as a response time four times the satisfactory response time threshold (in milliseconds). It highlights transactions that have the highest impact on users. +Returns transactions with the defined user misery value. User Misery is a user-weighted performance metric that counts the number of unique users who were frustrated; "frustration" is measured as a response time four times the satisfactory response time threshold (in milliseconds). It highlights transactions that have the highest impact on users. - **Type:** number diff --git a/docs/concepts/search/searchable-properties/issues.mdx b/docs/concepts/search/searchable-properties/issues.mdx index 6750d7c5722b4..1a69f2505a703 100644 --- a/docs/concepts/search/searchable-properties/issues.mdx +++ b/docs/concepts/search/searchable-properties/issues.mdx @@ -426,7 +426,7 @@ A trace represents the record of the entire operation you want to measure or tra ### `transaction` -For [transactions](/product/insights/overview/transaction-summary/#what-is-a-transaction), the name of the transaction. For errors, the name of the associated transaction. +For [transactions](/product/dashboards/sentry-dashboards/transaction-summary/#what-is-a-transaction), the name of the transaction. For errors, the name of the associated transaction. - **Type:** string diff --git a/docs/contributing/approach/product-docs/write-index.mdx b/docs/contributing/approach/product-docs/write-index.mdx index e5dc6fa98d881..d7b50e3e33c79 100644 --- a/docs/contributing/approach/product-docs/write-index.mdx +++ b/docs/contributing/approach/product-docs/write-index.mdx @@ -41,7 +41,7 @@ Use this approach for a feature that doesn’t require much explanation and has ## How: Wider-Ranging Features - Benefit Breakdown -Use this approach for a page that requires more explanation to break down and/or has a lot of child pages to explain its different benefits, like [Insights](/product/insights/). +Use this approach for a page that requires more explanation to break down and/or has a lot of child pages to explain its different benefits, like [Insights](/product/dashboards/sentry-dashboards/). - Describe how each page section/element or child page, helps the customer achieve the WHY of this feature. - Include links to relevant child pages in the text. diff --git a/docs/guides/custom-spans.mdx b/docs/guides/custom-spans.mdx index 48354999a20b0..9596f504fc15a 100644 --- a/docs/guides/custom-spans.mdx +++ b/docs/guides/custom-spans.mdx @@ -638,7 +638,7 @@ fun processEmailDigest(job: Job) { ### 5. AI/LLM Operations -For AI workloads, use [Sentry Agent Monitoring](/product/insights/ai/agents/) instead of manual instrumentation when possible. It automatically captures agent workflows, tool calls, and token usage. +For AI workloads, use [Sentry Agent Monitoring](/ai/monitoring/agents/) instead of manual instrumentation when possible. It automatically captures agent workflows, tool calls, and token usage. If you're not using a supported framework or need custom attributes: diff --git a/docs/platforms/android/enriching-events/transaction-name/index.mdx b/docs/platforms/android/enriching-events/transaction-name/index.mdx index cadfaa7e3f4f1..d22b94af55e5b 100644 --- a/docs/platforms/android/enriching-events/transaction-name/index.mdx +++ b/docs/platforms/android/enriching-events/transaction-name/index.mdx @@ -3,7 +3,7 @@ title: Transaction Name description: "Learn how to set or override the transaction name to capture the user and gain critical pieces of information that construct a unique identity in Sentry." --- -The current transaction name is used to group transactions in our [Insights](/product/insights/) product, as well as annotate error events with their point of failure. +The current transaction name is used to group transactions in our [Insights](/product/dashboards/sentry-dashboards/) product, as well as annotate error events with their point of failure. The transaction name can reference the current web app route, or the current task being executed. For example: diff --git a/docs/platforms/android/features/index.mdx b/docs/platforms/android/features/index.mdx index 9ae103d7186a7..0b05761c55247 100644 --- a/docs/platforms/android/features/index.mdx +++ b/docs/platforms/android/features/index.mdx @@ -35,7 +35,7 @@ Let us know if you have feedback by filing a Release health, tracking crash-free users and sessions. - Attachments that can enrich your event by storing additional files, such as config or log files. - User Feedback, providing the ability to collect user information when an event occurs. -- Tracing that can track: +- Tracing that can track: - Android activity transactions. - User interaction transactions such as: view click, scroll, swipe, and so on. - Navigation transactions. diff --git a/docs/platforms/android/overhead/index.mdx b/docs/platforms/android/overhead/index.mdx index c4cb1f6d7225f..0f74d51230887 100644 --- a/docs/platforms/android/overhead/index.mdx +++ b/docs/platforms/android/overhead/index.mdx @@ -37,7 +37,7 @@ Note that increasing the max number of breadcrumbs **does not** improve performa ## Tracing and Performance Monitoring -As stated in our product docs on the topic, Tracing adds some overhead, but should have minimal impact on the performance of your application. In typical scenarios, the expected overhead is less than 3% of the app's resource utilization. +As stated in our product docs on the topic, Tracing adds some overhead, but should have minimal impact on the performance of your application. In typical scenarios, the expected overhead is less than 3% of the app's resource utilization. ## Profiling diff --git a/docs/platforms/android/tracing/index.mdx b/docs/platforms/android/tracing/index.mdx index 3703f07723511..aba9035010034 100644 --- a/docs/platforms/android/tracing/index.mdx +++ b/docs/platforms/android/tracing/index.mdx @@ -6,7 +6,7 @@ sidebar_order: 4000 sidebar_section: features --- -With [tracing](/product/insights/overview/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/). +With [tracing](/product/dashboards/sentry-dashboards/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/). diff --git a/docs/platforms/android/tracing/instrumentation/automatic-instrumentation.mdx b/docs/platforms/android/tracing/instrumentation/automatic-instrumentation.mdx index da33f188c9608..1b7026e1ce41c 100644 --- a/docs/platforms/android/tracing/instrumentation/automatic-instrumentation.mdx +++ b/docs/platforms/android/tracing/instrumentation/automatic-instrumentation.mdx @@ -157,7 +157,7 @@ You can opt out of Activity Instrumentation and App Start Instrumentation using ``` -Cold and warm start are Mobile Vitals, which you can learn about in the [full documentation](/product/insights/mobile/mobile-vitals). +Cold and warm start are Mobile Vitals, which you can learn about in the [full documentation](/product/dashboards/sentry-dashboards/mobile/mobile-vitals). ### Slow and Frozen Frames @@ -169,7 +169,7 @@ Supported on Android OS version `7.0` and above. Unresponsive UI and animation hitches annoy users and degrade the user experience. Two measurements to track these types of experiences are _slow frames_ and _frozen frames_. If you want your app to run smoothly, you should try to avoid both. The SDK adds these two measurements for the [Activity](/platforms/android/tracing/instrumentation/automatic-instrumentation/#activity-instrumentation) transactions. -Slow and frozen frames are Mobile Vitals, which you can learn about in the [full documentation](/product/insights/mobile/mobile-vitals). +Slow and frozen frames are Mobile Vitals, which you can learn about in the [full documentation](/product/dashboards/sentry-dashboards/mobile/mobile-vitals). ### Trace Propagation Targets diff --git a/docs/platforms/android/tracing/instrumentation/perf-v2.mdx b/docs/platforms/android/tracing/instrumentation/perf-v2.mdx index d0d03e3a230ec..8400d0382dcb6 100644 --- a/docs/platforms/android/tracing/instrumentation/perf-v2.mdx +++ b/docs/platforms/android/tracing/instrumentation/perf-v2.mdx @@ -5,7 +5,7 @@ description: Learn how to get even more insights into Android app performance og_image: /og-images/platforms-android-tracing-instrumentation-perf-v2.png --- -Performance V2 contains a set of features that enrich performance instrumentation. It tightly integrates with the [Mobile Vitals](/product/insights/mobile/mobile-vitals/) Insights module, enabling App Start and Frames Delay reporting. +Performance V2 contains a set of features that enrich performance instrumentation. It tightly integrates with the [Mobile Vitals](/product/dashboards/sentry-dashboards/mobile/mobile-vitals/) Insights module, enabling App Start and Frames Delay reporting. Since version 8 of the SDK, Performance V2 is generally available and enabled by default. In versions `7.4.0..<8.0.0`, this feature is available as _experimental_ and you need to opt in to use it: diff --git a/docs/platforms/apple/common/features/index.mdx b/docs/platforms/apple/common/features/index.mdx index 0d9c1a7e91844..8bc07f02ea6de 100644 --- a/docs/platforms/apple/common/features/index.mdx +++ b/docs/platforms/apple/common/features/index.mdx @@ -36,7 +36,7 @@ All features listed below are **enabled by default** unless otherwise noted. Som - Rendering of UIViewControllers - Performance of HTTP requests - Distributed tracing - - Insights for Mobile Vitals + - Insights for Mobile Vitals - Cold and warm start - Slow and frozen frames - Prewarmed App Start Tracing diff --git a/docs/platforms/apple/common/overhead/index.mdx b/docs/platforms/apple/common/overhead/index.mdx index a696b326fb3af..5db186af55bd0 100644 --- a/docs/platforms/apple/common/overhead/index.mdx +++ b/docs/platforms/apple/common/overhead/index.mdx @@ -41,7 +41,7 @@ Note that increasing the max number of breadcrumbs **does not** improve performa ## Tracing and Performance Monitoring -As stated in our product docs on the topic, Tracing adds some overhead, but should have minimal impact on the performance of your application. In typical scenarios, the expected overhead is less than 3% of the app's resource utilization. +As stated in our product docs on the topic, Tracing adds some overhead, but should have minimal impact on the performance of your application. In typical scenarios, the expected overhead is less than 3% of the app's resource utilization. diff --git a/docs/platforms/apple/common/tracing/index.mdx b/docs/platforms/apple/common/tracing/index.mdx index c7e8333eb02eb..194238b0b797e 100644 --- a/docs/platforms/apple/common/tracing/index.mdx +++ b/docs/platforms/apple/common/tracing/index.mdx @@ -6,7 +6,7 @@ sidebar_order: 4000 sidebar_section: features --- -With [tracing](/product/insights/overview/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/). +With [tracing](/product/dashboards/sentry-dashboards/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/). Automatic instrumentation for monitoring the performance of your application is currently in preview. You can also use custom instrumentation to capture transactions. diff --git a/docs/platforms/apple/common/tracing/instrumentation/automatic-instrumentation.mdx b/docs/platforms/apple/common/tracing/instrumentation/automatic-instrumentation.mdx index 5786b2e35507b..740471d5e8c11 100644 --- a/docs/platforms/apple/common/tracing/instrumentation/automatic-instrumentation.mdx +++ b/docs/platforms/apple/common/tracing/instrumentation/automatic-instrumentation.mdx @@ -165,7 +165,7 @@ The Cocoa SDK creates the following app start spans: ![App Start Transaction](./img/app-start-transaction.png) -Cold and warm start are Mobile Vitals, which you can learn about in the [full documentation](/product/insights/mobile/mobile-vitals). +Cold and warm start are Mobile Vitals, which you can learn about in the [full documentation](/product/dashboards/sentry-dashboards/mobile/mobile-vitals). ### Prewarmed App Start Tracing Starting with iOS 15, the operating system might [prewarm](https://developer.apple.com/documentation/uikit/app_and_environment/responding_to_the_launch_of_your_app/about_the_app_launch_sequence#3894431) your app by creating the process before the user opens it. Starting with SDK version [9.0.0](https://github.com/getsentry/sentry-cocoa/releases/tag/9.0.0), the `enablePreWarmedAppStartTracing` is enabled by default. @@ -211,7 +211,7 @@ The detail view of the transaction displays the slow, frozen, and total frames: ![Slow and Frozen Frames](./img/slow-frozen-frames.png) -Slow and frozen frames are Mobile Vitals, which you can learn about in the [full documentation](/product/insights/mobile/mobile-vitals). +Slow and frozen frames are Mobile Vitals, which you can learn about in the [full documentation](/product/dashboards/sentry-dashboards/mobile/mobile-vitals). ## Network Tracking diff --git a/docs/platforms/apple/common/tracing/instrumentation/swiftui-instrumentation.mdx b/docs/platforms/apple/common/tracing/instrumentation/swiftui-instrumentation.mdx index b416f0aeaa0e6..dbadaae0baf9f 100644 --- a/docs/platforms/apple/common/tracing/instrumentation/swiftui-instrumentation.mdx +++ b/docs/platforms/apple/common/tracing/instrumentation/swiftui-instrumentation.mdx @@ -184,4 +184,4 @@ struct ContentView: View { - **Early calls**: If `reportFullyDisplayed()` is called before the view appears, the reported time will be shifted to match the TTID measured time. -For more information about TTID and TTFD metrics, see the [Mobile Vitals documentation](/product/insights/mobile/mobile-vitals/#time-to-initial-display-and-time-to-full-display). +For more information about TTID and TTFD metrics, see the [Mobile Vitals documentation](/product/dashboards/sentry-dashboards/mobile/mobile-vitals/#time-to-initial-display-and-time-to-full-display). diff --git a/docs/platforms/apple/guides/ios/features/index.mdx b/docs/platforms/apple/guides/ios/features/index.mdx index d46aae035482d..411212eab192a 100644 --- a/docs/platforms/apple/guides/ios/features/index.mdx +++ b/docs/platforms/apple/guides/ios/features/index.mdx @@ -41,7 +41,7 @@ iOS supports comprehensive error detection: iOS supports all performance monitoring features: - App start tracking for cold and warm app start times -- Frame rate tracking for UI rendering performance and slow/frozen frame identification +- Frame rate tracking for UI rendering performance and slow/frozen frame identification - User interaction tracking that automatically creates transactions for UI interactions - Network request monitoring for HTTP request performance - File I/O performance tracking for file operations diff --git a/docs/platforms/apple/guides/macos/features/index.mdx b/docs/platforms/apple/guides/macos/features/index.mdx index 11c3d77d99c97..6466a3cc30522 100644 --- a/docs/platforms/apple/guides/macos/features/index.mdx +++ b/docs/platforms/apple/guides/macos/features/index.mdx @@ -64,7 +64,7 @@ macOS supports comprehensive perform For macOS apps using UIKit (Mac Catalyst), the following features are also available: - App start tracking for cold and warm app start times -- Frame rate tracking for UI rendering performance +- Frame rate tracking for UI rendering performance - User interaction tracking that automatically creates transactions for UI interactions - Automatic performance transactions for UIViewController rendering diff --git a/docs/platforms/apple/guides/tvos/features/index.mdx b/docs/platforms/apple/guides/tvos/features/index.mdx index 86a44dccb15c5..8554e9a5c6a7f 100644 --- a/docs/platforms/apple/guides/tvos/features/index.mdx +++ b/docs/platforms/apple/guides/tvos/features/index.mdx @@ -42,7 +42,7 @@ Session Replay works on tvOS 16+, but it is only officially supported on iOS. Wh tvOS supports comprehensive performance monitoring: - App start tracking for cold and warm app start times -- Frame rate tracking for UI rendering performance and slow/frozen frame identification +- Frame rate tracking for UI rendering performance and slow/frozen frame identification - User interaction tracking that automatically creates transactions for UI interactions - Network request monitoring for HTTP request performance - File I/O performance tracking for file operations diff --git a/docs/platforms/apple/guides/visionos/features/index.mdx b/docs/platforms/apple/guides/visionos/features/index.mdx index 8f071c2ee9350..b839288e2e61f 100644 --- a/docs/platforms/apple/guides/visionos/features/index.mdx +++ b/docs/platforms/apple/guides/visionos/features/index.mdx @@ -36,7 +36,7 @@ visionOS has some limitations compared to iOS: visionOS supports comprehensive performance monitoring: - App start tracking for cold and warm app start times -- Frame rate tracking for UI rendering performance and slow/frozen frame identification +- Frame rate tracking for UI rendering performance and slow/frozen frame identification - User interaction tracking that automatically creates transactions for UI interactions - Network request monitoring for HTTP request performance - File I/O performance tracking for file operations diff --git a/docs/platforms/dart/common/enriching-events/transaction-name/index.mdx b/docs/platforms/dart/common/enriching-events/transaction-name/index.mdx index 1feba90e0313d..79edb847015bb 100644 --- a/docs/platforms/dart/common/enriching-events/transaction-name/index.mdx +++ b/docs/platforms/dart/common/enriching-events/transaction-name/index.mdx @@ -4,7 +4,7 @@ description: "Learn how to set or override the transaction name to capture the u --- The current transaction name is used to group transactions in our -[Insights](/product/insights/) product, as well as annotate error events +[Sentry Dashboards](/product/dashboards/sentry-dashboards/) product, as well as annotate error events with their point of failure. The transaction name can reference the current web app route, or the current diff --git a/docs/platforms/dart/common/features/index.mdx b/docs/platforms/dart/common/features/index.mdx index 4672d74943f0a..fdbcf230f401c 100644 --- a/docs/platforms/dart/common/features/index.mdx +++ b/docs/platforms/dart/common/features/index.mdx @@ -17,7 +17,7 @@ Sentry's Dart SDK enables automatic reporting of errors and exceptions, and iden your event by storing additional files, such as config or log files. - User Feedback provides the ability to collect user information when an event occurs. -- Tracing creates transactions for: +- Tracing creates transactions for: - HTTP requests. - Dio HTTP library. - File I/O Integration. diff --git a/docs/platforms/dart/common/overhead/index.mdx b/docs/platforms/dart/common/overhead/index.mdx index 3194f6a6d5d6d..898707d481fb9 100644 --- a/docs/platforms/dart/common/overhead/index.mdx +++ b/docs/platforms/dart/common/overhead/index.mdx @@ -31,7 +31,7 @@ Note that increasing the max number of breadcrumbs **does not** improve performa ## Tracing and Performance Monitoring -As stated in our product docs on the topic, Tracing adds some overhead, but should have minimal impact on the performance of your application. In typical scenarios, the expected overhead is less than 3% of the app's resource utilization. +As stated in our product docs on the topic, Tracing adds some overhead, but should have minimal impact on the performance of your application. In typical scenarios, the expected overhead is less than 3% of the app's resource utilization. ## SDK Size diff --git a/docs/platforms/dart/common/tracing/index.mdx b/docs/platforms/dart/common/tracing/index.mdx index 5cb9aff9de3d2..3a9c5b19f5d41 100644 --- a/docs/platforms/dart/common/tracing/index.mdx +++ b/docs/platforms/dart/common/tracing/index.mdx @@ -6,7 +6,7 @@ sidebar_order: 4000 sidebar_section: features --- -With [tracing](/product/insights/overview/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/). +With [tracing](/product/dashboards/sentry-dashboards/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/). diff --git a/docs/platforms/dart/guides/flutter/configuration/options.mdx b/docs/platforms/dart/guides/flutter/configuration/options.mdx index d732afa56c1f4..8250787116a66 100644 --- a/docs/platforms/dart/guides/flutter/configuration/options.mdx +++ b/docs/platforms/dart/guides/flutter/configuration/options.mdx @@ -332,7 +332,7 @@ Set this boolean to `true` to automatically attach all threads to all logged eve -Set this boolean to `false` to disable auto [tracing](/product/insights/overview/) tracking. +Set this boolean to `false` to disable auto [tracing](/product/dashboards/sentry-dashboards/) tracking. diff --git a/docs/platforms/dart/guides/flutter/enriching-events/transaction-name/index.mdx b/docs/platforms/dart/guides/flutter/enriching-events/transaction-name/index.mdx index 1feba90e0313d..f0d51a726ad70 100644 --- a/docs/platforms/dart/guides/flutter/enriching-events/transaction-name/index.mdx +++ b/docs/platforms/dart/guides/flutter/enriching-events/transaction-name/index.mdx @@ -4,7 +4,7 @@ description: "Learn how to set or override the transaction name to capture the u --- The current transaction name is used to group transactions in our -[Insights](/product/insights/) product, as well as annotate error events +[Insights](/product/dashboards/sentry-dashboards/) product, as well as annotate error events with their point of failure. The transaction name can reference the current web app route, or the current diff --git a/docs/platforms/dart/guides/flutter/overhead/index.mdx b/docs/platforms/dart/guides/flutter/overhead/index.mdx index 36f3234101ae0..266d64b466aa1 100644 --- a/docs/platforms/dart/guides/flutter/overhead/index.mdx +++ b/docs/platforms/dart/guides/flutter/overhead/index.mdx @@ -37,7 +37,7 @@ Note that increasing the max number of breadcrumbs **does not** improve performa ## Tracing and Performance Monitoring -As stated in our product docs on the topic, Tracing adds some overhead, but should have minimal impact on the performance of your application. In typical scenarios, the expected overhead is less than 3% of the app's resource utilization. +As stated in our product docs on the topic, Tracing adds some overhead, but should have minimal impact on the performance of your application. In typical scenarios, the expected overhead is less than 3% of the app's resource utilization. ## Profiling diff --git a/docs/platforms/dart/guides/flutter/tracing/index.mdx b/docs/platforms/dart/guides/flutter/tracing/index.mdx index 9d541af4bf25c..ee633192a2789 100644 --- a/docs/platforms/dart/guides/flutter/tracing/index.mdx +++ b/docs/platforms/dart/guides/flutter/tracing/index.mdx @@ -6,7 +6,7 @@ sidebar_order: 4000 sidebar_section: features --- -With [tracing](/product/insights/overview/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/). +With [tracing](/product/dashboards/sentry-dashboards/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/). diff --git a/docs/platforms/dart/guides/flutter/tracing/instrumentation/automatic-instrumentation.mdx b/docs/platforms/dart/guides/flutter/tracing/instrumentation/automatic-instrumentation.mdx index c6e2ef5647eb7..d0cbe2d2c1fa4 100644 --- a/docs/platforms/dart/guides/flutter/tracing/instrumentation/automatic-instrumentation.mdx +++ b/docs/platforms/dart/guides/flutter/tracing/instrumentation/automatic-instrumentation.mdx @@ -45,7 +45,7 @@ Learn more in our [App Start Instrumentation](/platforms/dart/guides/flutter/int Unresponsive UI and animation hitches annoy users and degrade the user experience. Two measurements to track these types of experiences are slow frames and frozen frames. If you want your app to run smoothly, you should try to avoid both. The SDK adds these two measurements for the transactions you capture. -Slow and frozen frames are Mobile Vitals, which you can learn about in the [full documentation](/product/insights/mobile/mobile-vitals). +Slow and frozen frames are Mobile Vitals, which you can learn about in the [full documentation](/product/dashboards/sentry-dashboards/mobile/mobile-vitals). Learn more how to set it up in our [Slow and Frozen Frames Instrumentation](/platforms/dart/guides/flutter/integrations/slow-and-frozen-frames-instrumentation/) docs. diff --git a/docs/platforms/dotnet/common/enriching-events/transaction-name/index.mdx b/docs/platforms/dotnet/common/enriching-events/transaction-name/index.mdx index 1feba90e0313d..f0d51a726ad70 100644 --- a/docs/platforms/dotnet/common/enriching-events/transaction-name/index.mdx +++ b/docs/platforms/dotnet/common/enriching-events/transaction-name/index.mdx @@ -4,7 +4,7 @@ description: "Learn how to set or override the transaction name to capture the u --- The current transaction name is used to group transactions in our -[Insights](/product/insights/) product, as well as annotate error events +[Insights](/product/dashboards/sentry-dashboards/) product, as well as annotate error events with their point of failure. The transaction name can reference the current web app route, or the current diff --git a/docs/platforms/dotnet/common/tracing/index.mdx b/docs/platforms/dotnet/common/tracing/index.mdx index dcb39dafdfc09..ff34942bcef06 100644 --- a/docs/platforms/dotnet/common/tracing/index.mdx +++ b/docs/platforms/dotnet/common/tracing/index.mdx @@ -8,7 +8,7 @@ sidebar_section: features -With [tracing](/product/insights/overview/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/). +With [tracing](/product/dashboards/sentry-dashboards/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/). diff --git a/docs/platforms/elixir/tracing/index.mdx b/docs/platforms/elixir/tracing/index.mdx index e94552b17e022..e62b7061c540c 100644 --- a/docs/platforms/elixir/tracing/index.mdx +++ b/docs/platforms/elixir/tracing/index.mdx @@ -6,7 +6,7 @@ sidebar_order: 30 sidebar_section: features --- -With [tracing](/product/insights/overview/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. +With [tracing](/product/dashboards/sentry-dashboards/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. diff --git a/docs/platforms/go/common/enriching-events/transaction-name/index.mdx b/docs/platforms/go/common/enriching-events/transaction-name/index.mdx index e473f2ccec6f7..31bb1f90b2380 100644 --- a/docs/platforms/go/common/enriching-events/transaction-name/index.mdx +++ b/docs/platforms/go/common/enriching-events/transaction-name/index.mdx @@ -4,7 +4,7 @@ description: "Learn how to set or override the transaction name to capture the u --- The current transaction name is used to group transactions in our -[Insights](/product/insights/) product, as well as annotate error events +[Insights](/product/dashboards/sentry-dashboards/) product, as well as annotate error events with their point of failure. The transaction name can reference the current web app route, or the current diff --git a/docs/platforms/go/common/tracing/index.mdx b/docs/platforms/go/common/tracing/index.mdx index 4b25f43d80a7c..631b4f3ec4d13 100644 --- a/docs/platforms/go/common/tracing/index.mdx +++ b/docs/platforms/go/common/tracing/index.mdx @@ -6,7 +6,7 @@ sidebar_order: 4000 sidebar_section: features --- -With [tracing](/product/insights/overview/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/). +With [tracing](/product/dashboards/sentry-dashboards/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/). diff --git a/docs/platforms/java/common/enriching-events/transaction-name/index.mdx b/docs/platforms/java/common/enriching-events/transaction-name/index.mdx index 1feba90e0313d..f0d51a726ad70 100644 --- a/docs/platforms/java/common/enriching-events/transaction-name/index.mdx +++ b/docs/platforms/java/common/enriching-events/transaction-name/index.mdx @@ -4,7 +4,7 @@ description: "Learn how to set or override the transaction name to capture the u --- The current transaction name is used to group transactions in our -[Insights](/product/insights/) product, as well as annotate error events +[Insights](/product/dashboards/sentry-dashboards/) product, as well as annotate error events with their point of failure. The transaction name can reference the current web app route, or the current diff --git a/docs/platforms/java/common/tracing/index.mdx b/docs/platforms/java/common/tracing/index.mdx index bd8f835d116b2..2fa4d0c01f10d 100644 --- a/docs/platforms/java/common/tracing/index.mdx +++ b/docs/platforms/java/common/tracing/index.mdx @@ -10,7 +10,7 @@ supported: - java.spring --- -With [tracing](/product/insights/overview), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/). +With [tracing](/product/dashboards/sentry-dashboards/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/). diff --git a/docs/platforms/javascript/common/configuration/integrations/browsertracing.mdx b/docs/platforms/javascript/common/configuration/integrations/browsertracing.mdx index 369919fb19029..3355d9e3a8f1f 100644 --- a/docs/platforms/javascript/common/configuration/integrations/browsertracing.mdx +++ b/docs/platforms/javascript/common/configuration/integrations/browsertracing.mdx @@ -28,7 +28,7 @@ This integration only works inside a browser environment. _Import name: `Sentry.browserTracingIntegration`_ -With [tracing](/product/insights/overview/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. +With [tracing](/product/dashboards/sentry-dashboards/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. The BrowserTracing integration sets up automatic tracing for your frontend applications. It captures transactions and spans from the browser and sends them to Sentry. diff --git a/docs/platforms/javascript/common/configuration/integrations/supabase.mdx b/docs/platforms/javascript/common/configuration/integrations/supabase.mdx index 7695d7a8fa039..6315aaf9b6bf8 100644 --- a/docs/platforms/javascript/common/configuration/integrations/supabase.mdx +++ b/docs/platforms/javascript/common/configuration/integrations/supabase.mdx @@ -84,7 +84,7 @@ Admin operations are also instrumented: ### Database Operation Spans -These spans are used to populate Sentry's [Query Insights](/product/insights/backend/queries/) feature, which provides performance metrics and analysis for your database operations. With Query Insights, you can identify slow queries, track query frequency, and optimize your database interactions. +These spans are used to populate Sentry's [Query Insights](/product/dashboards/sentry-dashboards/backend/queries/) feature, which provides performance metrics and analysis for your database operations. With Query Insights, you can identify slow queries, track query frequency, and optimize your database interactions. - `db.table`: The table being queried - `db.schema`: The database schema diff --git a/docs/platforms/javascript/common/tracing/index.mdx b/docs/platforms/javascript/common/tracing/index.mdx index cd6b0f6ce99f4..14db69d331931 100644 --- a/docs/platforms/javascript/common/tracing/index.mdx +++ b/docs/platforms/javascript/common/tracing/index.mdx @@ -8,7 +8,7 @@ sidebar_section: features -With [tracing](/product/insights/overview/), Sentry automatically tracks your software performance across your application services, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. +With [tracing](/product/dashboards/sentry-dashboards/), Sentry automatically tracks your software performance across your application services, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. diff --git a/docs/platforms/javascript/common/tracing/instrumentation/automatic-instrumentation.mdx b/docs/platforms/javascript/common/tracing/instrumentation/automatic-instrumentation.mdx index 33090b871b680..afff9b5e04d25 100644 --- a/docs/platforms/javascript/common/tracing/instrumentation/automatic-instrumentation.mdx +++ b/docs/platforms/javascript/common/tracing/instrumentation/automatic-instrumentation.mdx @@ -118,7 +118,7 @@ Exclude requests from tracing, such as health checks or analytics pings: -Automatically captures [INP](/product/insights/web-vitals/web-vitals-concepts/#interaction-to-next-paint-inp) events to measure responsiveness. Results appear in the [Web Vitals](/product/insights/web-vitals/) module. +Automatically captures [INP](/product/dashboards/sentry-dashboards/frontend/web-vitals/web-vitals-concepts/#interaction-to-next-paint-inp) events to measure responsiveness. Results appear in the [Web Vitals](/product/dashboards/sentry-dashboards/frontend/web-vitals/) module. Default: `true` in SDK 8.x+, `false` in 7.x. diff --git a/docs/platforms/javascript/common/tracing/instrumentation/requests-module.mdx b/docs/platforms/javascript/common/tracing/instrumentation/requests-module.mdx index 35ad1b71a37d9..4701c5aaf7a77 100644 --- a/docs/platforms/javascript/common/tracing/instrumentation/requests-module.mdx +++ b/docs/platforms/javascript/common/tracing/instrumentation/requests-module.mdx @@ -4,7 +4,7 @@ sidebar_order: 2000 description: "Learn how to manually instrument your code to use Sentry's Requests module." --- -As a prerequisite to setting up [Requests](/product/insights/requests/), you'll need to first set up tracing. Once this is done, the JavaScript SDK will automatically instrument outgoing HTTP requests. If that doesn't fit your use case, follow this guide to manually instrument your requests. +As a prerequisite to setting up [Requests](/product/dashboards/sentry-dashboards/outbound-api-requests/), you'll need to first set up tracing. Once this is done, the JavaScript SDK will automatically instrument outgoing HTTP requests. If that doesn't fit your use case, follow this guide to manually instrument your requests. For detailed information about which data can be set, see the [Requests Module developer specifications](https://develop.sentry.dev/sdk/performance/modules/requests/). diff --git a/docs/platforms/javascript/guides/nextjs/tracing/index.mdx b/docs/platforms/javascript/guides/nextjs/tracing/index.mdx index 166852e21c23a..0544b175f90af 100644 --- a/docs/platforms/javascript/guides/nextjs/tracing/index.mdx +++ b/docs/platforms/javascript/guides/nextjs/tracing/index.mdx @@ -185,7 +185,7 @@ export async function submitForm(formData: FormData) { ## Web Vitals -The SDK automatically captures [Web Vitals](/product/insights/web-vitals/) on every page load. These metrics measure real user experience: +The SDK automatically captures [Web Vitals](/product/dashboards/sentry-dashboards/frontend/web-vitals/) on every page load. These metrics measure real user experience: | Metric | What It Measures | Threshold (Good) | |--------|------------------|------------------| @@ -195,7 +195,7 @@ The SDK automatically captures [Web Vitals](/product/insights/web-vitals/) on ev | **FCP** | First Contentful Paint — initial render | ≤ 1s | | **TTFB** | Time to First Byte — server response | ≤ 100ms | -Web Vitals appear as measurements on page load transactions and feed into your [Performance Score](/product/insights/web-vitals/#performance-score). See [Web Vitals Concepts](/product/insights/web-vitals/web-vitals-concepts/) for detailed explanations of each metric. +Web Vitals appear as measurements on page load transactions and feed into your [Performance Score](/product/dashboards/sentry-dashboards/frontend/web-vitals/#performance-score). See [Web Vitals Concepts](/product/dashboards/sentry-dashboards/frontend/web-vitals/web-vitals-concepts/) for detailed explanations of each metric. ## Custom Instrumentation diff --git a/docs/platforms/native/common/enriching-events/transaction-name/index.mdx b/docs/platforms/native/common/enriching-events/transaction-name/index.mdx index f32d0b372cacb..1abd271402093 100644 --- a/docs/platforms/native/common/enriching-events/transaction-name/index.mdx +++ b/docs/platforms/native/common/enriching-events/transaction-name/index.mdx @@ -6,7 +6,7 @@ notSupported: --- The current transaction name is used to group transactions in our -[Insights](/product/insights/) product, as well as annotate error events +[Insights](/product/dashboards/sentry-dashboards/) product, as well as annotate error events with their point of failure. The transaction name can reference the current web app route, or the current diff --git a/docs/platforms/native/common/tracing/index.mdx b/docs/platforms/native/common/tracing/index.mdx index 29492cd5732c1..8f878dd00d7ff 100644 --- a/docs/platforms/native/common/tracing/index.mdx +++ b/docs/platforms/native/common/tracing/index.mdx @@ -11,7 +11,7 @@ notSupported: - native.wasm --- -With [tracing](/product/insights/overview/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/). +With [tracing](/product/dashboards/sentry-dashboards/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/). diff --git a/docs/platforms/php/common/tracing/index.mdx b/docs/platforms/php/common/tracing/index.mdx index 0acc50d9e2c83..727b9f3603423 100644 --- a/docs/platforms/php/common/tracing/index.mdx +++ b/docs/platforms/php/common/tracing/index.mdx @@ -6,7 +6,7 @@ sidebar_order: 1 sidebar_section: features --- -With [tracing](/product/insights/overview/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/). +With [tracing](/product/dashboards/sentry-dashboards/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/). diff --git a/docs/platforms/powershell/tracing/index.mdx b/docs/platforms/powershell/tracing/index.mdx index 1701a03dcec62..e796bdb7dda41 100644 --- a/docs/platforms/powershell/tracing/index.mdx +++ b/docs/platforms/powershell/tracing/index.mdx @@ -5,7 +5,7 @@ description: "Learn how to enable tracing in your app and discover valuable perf sidebar_order: 4000 --- -With [tracing](/product/insights/overview/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/). +With [tracing](/product/dashboards/sentry-dashboards/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/). diff --git a/docs/platforms/python/enriching-events/transaction-name/index.mdx b/docs/platforms/python/enriching-events/transaction-name/index.mdx index e473f2ccec6f7..31bb1f90b2380 100644 --- a/docs/platforms/python/enriching-events/transaction-name/index.mdx +++ b/docs/platforms/python/enriching-events/transaction-name/index.mdx @@ -4,7 +4,7 @@ description: "Learn how to set or override the transaction name to capture the u --- The current transaction name is used to group transactions in our -[Insights](/product/insights/) product, as well as annotate error events +[Insights](/product/dashboards/sentry-dashboards/) product, as well as annotate error events with their point of failure. The transaction name can reference the current web app route, or the current diff --git a/docs/platforms/python/tracing/instrumentation/custom-instrumentation/requests-module.mdx b/docs/platforms/python/tracing/instrumentation/custom-instrumentation/requests-module.mdx index 3294f0140dcbd..c828184d7d183 100644 --- a/docs/platforms/python/tracing/instrumentation/custom-instrumentation/requests-module.mdx +++ b/docs/platforms/python/tracing/instrumentation/custom-instrumentation/requests-module.mdx @@ -3,7 +3,7 @@ title: Instrument HTTP Requests sidebar_order: 2000 description: "Learn how to manually instrument your code to use Sentry's Requests module." --- -As a prerequisite to setting up [Requests](/product/insights/requests/), you’ll need to first set up tracing. Once this is done, the Python SDK will automatically instrument outgoing HTTP requests made via `HTTPConnection` and show the data in the [requests-monitoring dashboard](https://sentry.io/orgredirect/organizations/:orgslug/insights/backend/http/). If that doesn't fit your use case, you can set up using custom instrumentation described below. +As a prerequisite to setting up [Requests](/product/dashboards/sentry-dashboards/outbound-api-requests/), you’ll need to first set up tracing. Once this is done, the Python SDK will automatically instrument outgoing HTTP requests made via `HTTPConnection` and show the data in the [requests-monitoring dashboard](https://sentry.io/orgredirect/organizations/:orgslug/insights/backend/http/). If that doesn't fit your use case, you can set up using custom instrumentation described below. ## Custom Instrumentation diff --git a/docs/platforms/python/tracing/span-lifecycle/index.mdx b/docs/platforms/python/tracing/span-lifecycle/index.mdx index f25cd35ec13d3..571bf58725f73 100644 --- a/docs/platforms/python/tracing/span-lifecycle/index.mdx +++ b/docs/platforms/python/tracing/span-lifecycle/index.mdx @@ -106,7 +106,7 @@ if current_span: ## Working with Transactions -[Transactions](/product/insights/overview/transaction-summary/#what-is-a-transaction) are a special type of span that represent a complete operation in your application, such as a web request. You can create transactions explicitly: +[Transactions](/product/dashboards/sentry-dashboards/transaction-summary/#what-is-a-transaction) are a special type of span that represent a complete operation in your application, such as a web request. You can create transactions explicitly: ```python import sentry_sdk diff --git a/docs/platforms/react-native/configuration/options.mdx b/docs/platforms/react-native/configuration/options.mdx index 8c76dad28d0e1..c1058bba9bb60 100644 --- a/docs/platforms/react-native/configuration/options.mdx +++ b/docs/platforms/react-native/configuration/options.mdx @@ -408,7 +408,7 @@ When enabled, ANR events whose stacktraces contain only system frames (for examp -Set this boolean to `false` to disable auto [performance monitoring](/product/insights/) tracking. +Set this boolean to `false` to disable auto [performance monitoring](/product/dashboards/sentry-dashboards/) tracking. diff --git a/docs/platforms/react-native/enriching-events/transaction-name/index.mdx b/docs/platforms/react-native/enriching-events/transaction-name/index.mdx index 64e27fd24997f..6888ff8132ed9 100644 --- a/docs/platforms/react-native/enriching-events/transaction-name/index.mdx +++ b/docs/platforms/react-native/enriching-events/transaction-name/index.mdx @@ -4,7 +4,7 @@ description: "Learn how to set or override the transaction name to capture the u --- The current transaction name is used to group transactions in our -[Insights](/product/insights/) product, as well as annotate error events +[Insights](/product/dashboards/sentry-dashboards/) product, as well as annotate error events with their point of failure. The transaction name can reference the current web app route, or the current diff --git a/docs/platforms/react-native/features/index.mdx b/docs/platforms/react-native/features/index.mdx index cb37d0fc1537f..790b57f861999 100644 --- a/docs/platforms/react-native/features/index.mdx +++ b/docs/platforms/react-native/features/index.mdx @@ -17,7 +17,7 @@ Sentry's React Native SDK enables automatic reporting of errors and exceptions, - Autolinking. - Breadcrumbs created for outgoing `http` request with XHR and Fetch; UI and system events; and console logs. - Release health tracks crash free users and sessions. -- Tracing creates transactions automatically for: +- Tracing creates transactions automatically for: - App Start time. - Routing Instrumentation (React Navigation v4 and above and React Native Navigation). - XHR and Fetch requests. diff --git a/docs/platforms/react-native/overhead/index.mdx b/docs/platforms/react-native/overhead/index.mdx index 2d32b342ab45c..d8a21fe5ea01c 100644 --- a/docs/platforms/react-native/overhead/index.mdx +++ b/docs/platforms/react-native/overhead/index.mdx @@ -37,7 +37,7 @@ Note that increasing the max number of breadcrumbs **does not** improve performa ## Tracing and Performance Monitoring -As stated in our product docs on the topic, Tracing adds some overhead, but should have minimal impact on the performance of your application. In typical scenarios, the expected overhead is less than 3% of the app's resource utilization. +As stated in our product docs on the topic, Tracing adds some overhead, but should have minimal impact on the performance of your application. In typical scenarios, the expected overhead is less than 3% of the app's resource utilization. ## Profiling diff --git a/docs/platforms/react-native/tracing/index.mdx b/docs/platforms/react-native/tracing/index.mdx index af86e2a5fee71..17b9d0ba929f1 100644 --- a/docs/platforms/react-native/tracing/index.mdx +++ b/docs/platforms/react-native/tracing/index.mdx @@ -6,7 +6,7 @@ sidebar_order: 2 sidebar_section: features --- -With [tracing](/product/insights/overview/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/). +With [tracing](/product/dashboards/sentry-dashboards/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/). ## Configure diff --git a/docs/platforms/react-native/tracing/instrumentation/automatic-instrumentation.mdx b/docs/platforms/react-native/tracing/instrumentation/automatic-instrumentation.mdx index 4a782f306d6d5..9739f258a30f4 100644 --- a/docs/platforms/react-native/tracing/instrumentation/automatic-instrumentation.mdx +++ b/docs/platforms/react-native/tracing/instrumentation/automatic-instrumentation.mdx @@ -53,7 +53,7 @@ If you don't [wrap your root component with Sentry](#wrap-your-root-component), The SDK differentiates between a cold and a warm start, but doesn't track hot starts or resumes. The measurements are available under `measurements.app_start_warm` and `measurements.app_start_cold`. -Cold and warm start are Mobile Vitals, which you can learn about in the [full documentation](/product/insights/mobile/mobile-vitals). +Cold and warm start are Mobile Vitals, which you can learn about in the [full documentation](/product/dashboards/sentry-dashboards/mobile/mobile-vitals). @@ -65,11 +65,11 @@ Sentry's App Start instrumentation aims to be as comprehensive and representativ Unresponsive UI and animation hitches annoy users and degrade the user experience. Two measurements to track these types of experiences are slow frames and frozen frames. If you want your app to run smoothly, you should try to avoid both. The SDK adds these two measurements for the transactions you capture. -Slow and frozen frames are Mobile Vitals, which you can learn about in the [full documentation](/product/insights/mobile/mobile-vitals). +Slow and frozen frames are Mobile Vitals, which you can learn about in the [full documentation](/product/dashboards/sentry-dashboards/mobile/mobile-vitals). -React Native mobile apps will not report [Web Vitals](/product/insights/web-vitals/). These values depend on APIs provided by browsers, and are not available in this context. +React Native mobile apps will not report [Web Vitals](/product/dashboards/sentry-dashboards/frontend/web-vitals/). These values depend on APIs provided by browsers, and are not available in this context. diff --git a/docs/platforms/react-native/tracing/instrumentation/time-to-display.mdx b/docs/platforms/react-native/tracing/instrumentation/time-to-display.mdx index 03f63b6761118..12853baae3807 100644 --- a/docs/platforms/react-native/tracing/instrumentation/time-to-display.mdx +++ b/docs/platforms/react-native/tracing/instrumentation/time-to-display.mdx @@ -6,7 +6,7 @@ sdk: sentry.javascript.react-native description: "Learn how to measure time to display with the Sentry React Native SDK." --- -Sentry's React Native SDK package ships with a tracing feature that allows you to measure your application's [Time to Display](/product/insights/mobile/mobile-vitals/#time-to-initial-display-and-time-to-full-display). This guide will show you how to use Sentry's React Native SDK to measure Time to Display in your application. +Sentry's React Native SDK package ships with a tracing feature that allows you to measure your application's [Time to Display](/product/dashboards/sentry-dashboards/mobile/mobile-vitals/#time-to-initial-display-and-time-to-full-display). This guide will show you how to use Sentry's React Native SDK to measure Time to Display in your application. Time to Display consists of two parts, Time To Initial Display (TTID) and Time To Full Display (TTFD). TTID measures the time it takes to display the first frame, while TTFD measures the time it takes to display the full content for the user to interact with. diff --git a/docs/platforms/ruby/common/enriching-events/transaction-name/index.mdx b/docs/platforms/ruby/common/enriching-events/transaction-name/index.mdx index 1feba90e0313d..f0d51a726ad70 100644 --- a/docs/platforms/ruby/common/enriching-events/transaction-name/index.mdx +++ b/docs/platforms/ruby/common/enriching-events/transaction-name/index.mdx @@ -4,7 +4,7 @@ description: "Learn how to set or override the transaction name to capture the u --- The current transaction name is used to group transactions in our -[Insights](/product/insights/) product, as well as annotate error events +[Insights](/product/dashboards/sentry-dashboards/) product, as well as annotate error events with their point of failure. The transaction name can reference the current web app route, or the current diff --git a/docs/platforms/ruby/common/migration.mdx b/docs/platforms/ruby/common/migration.mdx index 9912b0c79a723..b5405fb9f48db 100644 --- a/docs/platforms/ruby/common/migration.mdx +++ b/docs/platforms/ruby/common/migration.mdx @@ -18,7 +18,7 @@ sidebar_section: configuration - **Unified Interfaces With Other SDKs:** The design of `sentry-raven` is outdated compared with our modern Sentry SDKs. If you also use other Sentry SDKs, such as Sentry's JavaScript SDK for your frontend application, you'll notice that their interfaces are quite different from the one provided for `sentry-raven`. The new `sentry-ruby` SDK provides a more consistent user experience across all different platforms. -- **Tracing:** The Sentry Ruby SDK includes [tracing](/product/insights/overview/), which you can enable if you haven't already as ([discussed here](/platforms/ruby/tracing/)). +- **Tracing:** The Sentry Ruby SDK includes [tracing](/product/dashboards/sentry-dashboards/), which you can enable if you haven't already as ([discussed here](/platforms/ruby/tracing/)). - **Future Support:** `sentry-raven` has entered maintenance mode, which means it won't receive any new feature supports or aggressive bug fixes. diff --git a/docs/platforms/ruby/common/tracing/index.mdx b/docs/platforms/ruby/common/tracing/index.mdx index be94600dea63c..a6fc5df4c9700 100644 --- a/docs/platforms/ruby/common/tracing/index.mdx +++ b/docs/platforms/ruby/common/tracing/index.mdx @@ -8,7 +8,7 @@ sidebar_section: features -With [tracing](/product/insights/overview/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/). +With [tracing](/product/dashboards/sentry-dashboards/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/). diff --git a/docs/platforms/ruby/common/tracing/instrumentation/custom-instrumentation/requests-module.mdx b/docs/platforms/ruby/common/tracing/instrumentation/custom-instrumentation/requests-module.mdx index a7cfa77a5d99a..fe620fe32b4e9 100644 --- a/docs/platforms/ruby/common/tracing/instrumentation/custom-instrumentation/requests-module.mdx +++ b/docs/platforms/ruby/common/tracing/instrumentation/custom-instrumentation/requests-module.mdx @@ -4,7 +4,7 @@ sidebar_order: 2000 description: "Learn how to manually instrument your code to use Sentry's Requests module." --- -As a prerequisite to setting up [Requests](/product/insights/backend/requests/), you’ll need to first set up performance monitoring. Once this is done, the Ruby SDK will automatically instrument outgoing HTTP requests made via `Net::HTTP`. If that doesn't fit your use case, you can set up using [custom instrumentation](#custom-instrumentation). +As a prerequisite to setting up [Requests](/product/dashboards/sentry-dashboards/outbound-api-requests/), you’ll need to first set up performance monitoring. Once this is done, the Ruby SDK will automatically instrument outgoing HTTP requests made via `Net::HTTP`. If that doesn't fit your use case, you can set up using [custom instrumentation](#custom-instrumentation). ## Custom Instrumentation diff --git a/docs/platforms/rust/common/tracing/index.mdx b/docs/platforms/rust/common/tracing/index.mdx index 24951e62bac8f..ea560134d98ed 100644 --- a/docs/platforms/rust/common/tracing/index.mdx +++ b/docs/platforms/rust/common/tracing/index.mdx @@ -6,7 +6,7 @@ sidebar_order: 4000 sidebar_section: features --- -With [tracing](/product/insights/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/). +With [tracing](/product/dashboards/sentry-dashboards/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/). diff --git a/docs/platforms/unity/enriching-events/transaction-name/index.mdx b/docs/platforms/unity/enriching-events/transaction-name/index.mdx index 1feba90e0313d..f0d51a726ad70 100644 --- a/docs/platforms/unity/enriching-events/transaction-name/index.mdx +++ b/docs/platforms/unity/enriching-events/transaction-name/index.mdx @@ -4,7 +4,7 @@ description: "Learn how to set or override the transaction name to capture the u --- The current transaction name is used to group transactions in our -[Insights](/product/insights/) product, as well as annotate error events +[Insights](/product/dashboards/sentry-dashboards/) product, as well as annotate error events with their point of failure. The transaction name can reference the current web app route, or the current diff --git a/docs/platforms/unity/tracing/index.mdx b/docs/platforms/unity/tracing/index.mdx index d2467762be28d..413e7127761ae 100644 --- a/docs/platforms/unity/tracing/index.mdx +++ b/docs/platforms/unity/tracing/index.mdx @@ -6,7 +6,7 @@ sidebar_order: 4000 sidebar_section: features --- -With [tracing](/product/insights/overview/), Sentry is able to [connect events coming from different parts of your game](/platforms/unity/usage/automatic-error-capture/#connecting-errors-captured-on-different-layers), whether it's native plugins or a backend. It helps you debug hard problems that involve C# scripts as well as the native layer on all platforms. It also allows you to monitor your game's performance, measuring metrics like initialization time, time spent on scene loading, and ANRs. Besides connecting different errors together, Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/). +With [tracing](/product/dashboards/sentry-dashboards/), Sentry is able to [connect events coming from different parts of your game](/platforms/unity/usage/automatic-error-capture/#connecting-errors-captured-on-different-layers), whether it's native plugins or a backend. It helps you debug hard problems that involve C# scripts as well as the native layer on all platforms. It also allows you to monitor your game's performance, measuring metrics like initialization time, time spent on scene loading, and ANRs. Besides connecting different errors together, Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/). diff --git a/docs/platforms/unreal/tracing/index.mdx b/docs/platforms/unreal/tracing/index.mdx index 8d94cb4c617e3..38a27d511e957 100644 --- a/docs/platforms/unreal/tracing/index.mdx +++ b/docs/platforms/unreal/tracing/index.mdx @@ -6,7 +6,7 @@ sidebar_order: 4000 sidebar_section: features --- -With [tracing](/product/insights/overview/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/). +With [tracing](/product/dashboards/sentry-dashboards/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/). diff --git a/docs/pricing/legacy-pricing.mdx b/docs/pricing/legacy-pricing.mdx index 357d87e479a6e..ab56a52c7133b 100644 --- a/docs/pricing/legacy-pricing.mdx +++ b/docs/pricing/legacy-pricing.mdx @@ -237,7 +237,7 @@ On-demand volume is billed at the end of each billing month. To see on-demand pr #### Shared and Per-Category On-Demand -Organizations on all plans have the option to set a shared on-demand strategy. Organizations on plans with [Insights](/product/insights/) features have the ability to choose between a shared or per-category on-demand strategy: +Organizations on all plans have the option to set a shared on-demand strategy. Organizations on plans with [Insights](/product/dashboards/sentry-dashboards/) features have the ability to choose between a shared or per-category on-demand strategy: - **Shared:** (default) Your on-demand budget is shared between all categories on a first come, first serve basis. There are no restrictions for any single category consuming the entire budget. diff --git a/docs/product/dashboards/sentry-dashboards/nextjs.mdx b/docs/product/dashboards/sentry-dashboards/nextjs.mdx index cf2d214cd7ba9..2f380dd11a628 100644 --- a/docs/product/dashboards/sentry-dashboards/nextjs.mdx +++ b/docs/product/dashboards/sentry-dashboards/nextjs.mdx @@ -31,7 +31,7 @@ The **Client Transactions** table lists browser-side transactions grouped by ope | `ui.interaction.click` | Click interactions | | `ui.interaction.press` | Press interactions | -Each row shows views, error rate, average and P95 duration, and a [performance score](/product/insights/frontend/web-vitals/) where applicable. +Each row shows views, error rate, average and P95 duration, and a [performance score](/product/dashboards/sentry-dashboards/frontend/web-vitals/) where applicable. ## Server Transactions diff --git a/docs/product/explore/profiling/getting-started.mdx b/docs/product/explore/profiling/getting-started.mdx index acb4fc6dbee15..93819ce87a453 100644 --- a/docs/product/explore/profiling/getting-started.mdx +++ b/docs/product/explore/profiling/getting-started.mdx @@ -68,7 +68,7 @@ UI Profiling can be used both independently and as a complement to the tracing p If Continuous Profiling or UI Profiling are not supported on your SDK, you can fall back to the older transaction-based Profiling implementation for the platforms below. -Transaction-based Profiling requires Sentry's tracing product being enabled beforehand. To enable tracing and performance monitoring features in the SDK, check out our [Insights guide](/product/insights/). +Transaction-based Profiling requires Sentry's tracing product being enabled beforehand. To enable tracing and performance monitoring features in the SDK, check out our [Insights guide](/product/dashboards/sentry-dashboards/). diff --git a/docs/product/explore/profiling/mobile-app-profiling/metrics.mdx b/docs/product/explore/profiling/mobile-app-profiling/metrics.mdx index b5679ea3e8146..aab1f29b518bd 100644 --- a/docs/product/explore/profiling/mobile-app-profiling/metrics.mdx +++ b/docs/product/explore/profiling/mobile-app-profiling/metrics.mdx @@ -20,7 +20,7 @@ The amount of heap memory used by the application is recorded every 100 ms using ## GPU Information -In addition to counting the number of [slow and frozen UI frame renders](/product/insights/mobile/mobile-vitals/#slow-and-frozen-frames) for Mobile Vitals Insights, Sentry now records the timestamp for every frame and overlays it on top of profiling flame charts: +In addition to counting the number of [slow and frozen UI frame renders](/product/dashboards/sentry-dashboards/mobile/mobile-vitals/#slow-and-frozen-frames) for Mobile Vitals Insights, Sentry now records the timestamp for every frame and overlays it on top of profiling flame charts: ![Sentry displays slow and frozen frames above the flamechart of a particular profile.](./img/flamechart-with-gpu-overlay.png) diff --git a/docs/product/explore/session-replay/replay-details.mdx b/docs/product/explore/session-replay/replay-details.mdx index df73f41c3679d..32486933c196f 100644 --- a/docs/product/explore/session-replay/replay-details.mdx +++ b/docs/product/explore/session-replay/replay-details.mdx @@ -42,7 +42,7 @@ The replay breadcrumbs show when key user interactions took place. Breadcrumbs a **Web-specific breadcrumbs include:** - **User Clicks:** including [rage clicks](/product/issues/issue-details/replay-issues/rage-clicks/) and [dead clicks](/product/issues/issue-details/replay-issues/rage-clicks/#detection-criteria) - **Navigations and Page Loads:** [Learn more about spans](/product/sentry-basics/distributed-tracing/) -- **Web Vitals:** and an overall performance score [Learn more](/product/insights/web-vitals/) +- **Web Vitals:** and an overall performance score [Learn more](/product/dashboards/sentry-dashboards/frontend/web-vitals/) **Mobile-specific breadcrumbs include:** - Backgrounding and foregrounding diff --git a/docs/product/explore/session-replay/web/index.mdx b/docs/product/explore/session-replay/web/index.mdx index 8e052c335e093..a3381ea6d4672 100644 --- a/docs/product/explore/session-replay/web/index.mdx +++ b/docs/product/explore/session-replay/web/index.mdx @@ -12,7 +12,7 @@ Session Replay allows you to see video-like reproductions of user sessions which Session Replay for web now includes an AI-powered replay summary that automatically analyzes what happened during a user session, and gives a short play-by-play to help debug issues faster. Rather than watch an entire replay, you can now get a quick overview of what happened and focus on the specific interactions that led to the issue. This feature requires the **Show Generative AI Features** setting to be enabled in **Settings > General**. -Replays are integrated with other parts of the Sentry product so you can see how the user experience is impacted by errors and slow transactions. You'll see session replays associated with error events on the [Issue Details](/product/issues/issue-details/) page, and those associated with slow transactions on the [Transaction Summary](/product/insights/overview/transaction-summary/) page. For [backend error replays](/product/explore/session-replay/web/getting-started/#replays-for-backend-errors), any contributing backend errors will be included in the replay's timeline, [breadcrumbs](/product/issues/issue-details/breadcrumbs/), and errors. +Replays are integrated with other parts of the Sentry product so you can see how the user experience is impacted by errors and slow transactions. You'll see session replays associated with error events on the [Issue Details](/product/issues/issue-details/) page, and those associated with slow transactions on the [Transaction Summary](/product/dashboards/sentry-dashboards/transaction-summary/) page. For [backend error replays](/product/explore/session-replay/web/getting-started/#replays-for-backend-errors), any contributing backend errors will be included in the replay's timeline, [breadcrumbs](/product/issues/issue-details/breadcrumbs/), and errors. ![Session Replay User Interface](./img/session-replay.png) diff --git a/docs/product/insights/backend/caches/cache-page.mdx b/docs/product/insights/backend/caches/cache-page.mdx deleted file mode 100644 index bf10ca02d048a..0000000000000 --- a/docs/product/insights/backend/caches/cache-page.mdx +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: "Cache Page" -sidebar_order: 30 -description: "Learn more about Sentry's Cache page, which provides insights into cache utilization and latency, so you can investigate potential cache performance issues." ---- - - - -Insights is going away soon. You can find all the same insights over in [Sentry Dashboards](/product/dashboards/sentry-dashboards). - - - -The **Caches** page gives an overview of cache performance across all endpoints for currently selected backend projects with summary graphs for **Miss Rate** and **Requests Per Minute** (throughput). You can use these as a starting point to see if there are any potential cache performance issues, for example, a higher than expected Miss Rate percentage. - -If you see an anomaly or want to investigate a time range further, click and drag to select a range directly in the graph and data will be filtered for that specific time range only. - -The transaction table shows a list of endpoints that contain at least one `cache.get` span along with: - -- Its average value size (the bytes being fetched from cache) -- Throughput -- Average transaction duration -- Miss rate percentage (how often did a lookup did not return a value) -- Time spent (total time your application spent on a given transaction) - -By default, this table is sorted by most time spent. This means that endpoints at the top are usually really slow, requested very frequently, or both. You can change the sort order to view top transactions by throughput, miss rate percentage, average value size, or average transaction duration. - -To investigate a specific endpoint, click on it to open a sidebar showing some sample events and additional duration metrics. - -## Sample List - -To help you compare the performances of cache hits (where a value was found in the cache) versus misses (where no value corresponding to the key was found in the cache) over time, Sentry automatically surfaces a distribution of both samples for the timeframe selected from the **Caches** page. - -These sample events are shown as triangles in the average duration graphs at the top. These sample events are also listed in the table below, along with their spans, key, transaction duration, and hit/miss status. - -From the sample list, you can drill down to specific good, average, or bad examples of cache performance within an endpoint. To view the detailed trace that contained the span operation, click on a **Span ID**. diff --git a/docs/product/insights/backend/caches/index.mdx b/docs/product/insights/backend/caches/index.mdx deleted file mode 100644 index 97b3891134f50..0000000000000 --- a/docs/product/insights/backend/caches/index.mdx +++ /dev/null @@ -1,38 +0,0 @@ ---- -title: "Caches" -sidebar_order: 70 -description: "Learn more about cache monitoring with Sentry and how it can help improve your application's performance." ---- - - - -Insights is going away soon. You can find all the same insights over in [Sentry Dashboards](/product/dashboards/sentry-dashboards). - - - -A cache can be used to speed up data retrieval, thereby improving application performance. A cache stores data temporarily to speed up subsequent access to that data. This allows your application to get data from cached memory (if it is available) instead having to download that data again or retrieving it from a potentially slow data layer. Caching can speed up read-heavy workloads for applications like Q&A portals, gaming, media sharing, and social networking. - -A successful cache results in a high hit rate which means the data was present when fetched. A cache miss occurs when the data fetched was not present in the cache. If you have performance monitoring enabled and your application uses caching, you can see how your caches are performing with Sentry. - -Sentry's cache monitoring provides insights into cache utilization and latency so that you can improve the performance of the endpoints that interact with caches. - -Starting with the [Cache page](https://sentry.io/orgredirect/organizations/:orgslug/insights/caches/), you get an overview of the transactions within your application that are making at least one lookup against a cache. From there, you can dig into specific cache span operations by clicking a transaction and viewing its sample list. - - - -## Instrumentation - -Cache monitoring currently supports [auto instrumentation](/platform-redirect/?next=%2Ftracing%2Finstrumentation%2Fautomatic-instrumentation) for [Django's cache framework](https://docs.djangoproject.com/en/5.0/topics/cache/) when the [cache_spans option](/platforms/python/integrations/django/#options) is set to `True`. Other frameworks require custom instrumentation. - -### Custom instrumentation - -If available, custom instrumentation is documented on an environment-by-environment basis as listed below: - -- [Python SDK](/platforms/python/tracing/instrumentation/custom-instrumentation/caches-module/) -- [JavaScript SDKs](/platforms/javascript/guides/node/tracing/instrumentation/custom-instrumentation/caches-module/) -- [PHP SDK](/platforms/php/tracing/instrumentation/caches-module/) -- [Java SDK](/platforms/java/tracing/instrumentation/custom-instrumentation/caches-module/) -- [Ruby SDK](/platforms/ruby/tracing/instrumentation/custom-instrumentation/caches-module/) -- [.NET SDK](/platforms/dotnet/tracing/instrumentation/custom-instrumentation/caches-module/) - -To see what cache data can be set on spans, see the [Cache Module Developer Specification](https://develop.sentry.dev/sdk/performance/modules/caches/). diff --git a/docs/product/insights/backend/index.mdx b/docs/product/insights/backend/index.mdx deleted file mode 100644 index b3af91f80b7cb..0000000000000 --- a/docs/product/insights/backend/index.mdx +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Backend Performance -sidebar_order: 20 -description: >- - Learn how to use Sentry's Backend Performance tool to monitor things like - queries, outbound API requests, caches, and queues. -og_image: /og-images/product-insights-backend.png ---- - - - -Insights is going away soon. You can find all the same insights over in [Sentry Dashboards](/product/dashboards/sentry-dashboards). - - - -Sentry's [**Backend Performance**](https://sentry.io/orgredirect/organizations/:orgslug/insights/backend/) page gives you an overview of the health of your application. You'll be able to see things like the **Most Time-Consuming Queries**, **Most Time-Consuming Domains**, **p50** and **p75 Duration**, and so on. - -![Backend performance overview page.](../img/backend-performance-overview.png) - -You can also dive deeper into Queries, Outbound API Requests, Caches, and Queues to get detailed information about potential issues affecting your application's health. In addition to having a dedicated space to monitor backend performance, you can also look at Sentry's **Insights** tab to monitor frontend, mobile, and AI performance. - -## Learn More - - diff --git a/docs/product/insights/backend/queries.mdx b/docs/product/insights/backend/queries.mdx deleted file mode 100644 index cd210397ffeeb..0000000000000 --- a/docs/product/insights/backend/queries.mdx +++ /dev/null @@ -1,134 +0,0 @@ ---- -title: Queries -sidebar_order: 0 -description: >- - With Queries in Sentry, you can easily see database queries, remediate - performance errors & monitor query performance. -og_image: /og-images/product-insights-backend-queries.png ---- - - - -Insights is going away soon. You can find all the same insights over in [Sentry Dashboards](/product/dashboards/sentry-dashboards). - - - -If you have [Insights](/product/insights/) enabled and your application queries a database, you can see how your queries are performing in Sentry. - -Sentry's query monitoring helps you investigate the performance of your queries and get more information to improve them. - -Starting with the [**Queries** page](#queries-page), you get a high-level overview of how your queries are doing. From there, you can drill into a specific query's [**Query Summary** page](#query-summary-page) and then investigate sample events from the [Sample List](#sample-list) to better understand the context of its performance in a specific endpoint. - -The interactive demo below demonstrates how to get insights on your query performance. - - - -
- -## Prerequisites and Limitations - -The queries widget and pages are only available for backend projects with performance monitoring enabled. - -### Recommended SDK Versions - -Query monitoring works best with up-to-date SDK versions. The following minimum versions are recommended: - -- [Python SDK v1.29.2](https://github.com/getsentry/sentry-python/releases/tag/1.29.2) -- [JavaScript SDKs v7.63.0](https://github.com/getsentry/sentry-javascript/releases/tag/7.63.0) -- [Laravel SDK v3.8.0](https://github.com/getsentry/sentry-laravel/releases/tag/3.8.0) -- [Cocoa SDK v8.11.0](https://github.com/getsentry/sentry-cocoa/releases/tag/8.11.0) -- [Java SDK v6.29.0](https://github.com/getsentry/sentry-java/releases/tag/6.29.0) -- [Ruby SDK v5.11.0](https://github.com/getsentry/sentry-ruby/releases/tag/5.11.0) -- [.NET SDK v3.39.0](https://github.com/getsentry/sentry-dotnet/releases/tag/3.39.0) -- [Symfony SDK v4.11.0](https://github.com/getsentry/sentry-symfony/releases/tag/4.11.0) -- [Android SDK v6.30.0](https://github.com/getsentry/sentry-java/releases/tag/6.30.0) - -### Span Eligibility - -Sentry tries to extract metrics for all SQL-like dialects, as well as MongoDB. Other NoSQL databases like Elasticsearch, graph databases like Neo4j, and other non-SQL database systems are not currently eligible for this feature. - -If you are using automatic instrumentation, query performance monitoring should work without any configuration. If you've manually instrumented Sentry, you'll need to make sure that your spans conform to our standards for the best experience: - -- The span `op` field is set to an [eligible value](https://develop.sentry.dev/sdk/performance/span-operations/#database). -- The span's description contains the full, parameterized query (e.g. `"SELECT * FROM users WHERE id = ?"`). Supported placeholder values for SQL are `%s`, `?`, `:c0` (e.g. `:c0`, `:c1`) and `$1` (e.g. `$1`, `$2`). MongoDB span descriptions should contain valid JSON, and placeholders should be the string `"?"`. -- The `db.system` span data value is set to the [correct identifier](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/db/database-spans.md) (e.g., `"postgresql"` or `"mongodb"`). - -## Queries Page - -The **Queries** page gives you a quick overview of your application's query performance for the selected project(s). You can use this page as a starting point to investigate potential problem queries and drill down to better understand how various queries are affecting your app's performance. - -Open the **Queries** page by clicking "Queries" in the sidebar, under "Insights". Alternatively, the **Performance** page also surfaces the highest impact queries in the "Most Time-Consuming Queries" widget. You can click "View All" to open the **Queries** page from there. - -At the top of the page, summary graphs for queries per minute (throughput) and average duration provide high-level insight into your database performance. If you see an anomaly or want to investigate a time range further, you can click and drag to select a range directly in a graph to filter data for that time range. - -The query description table below shows a list of queries, their volume (queries per minute), average duration, and the total time your app spent running that query (time spent). The query descriptions are parametrized, so your queries may look slightly different. - -By default, this table is sorted by most [time spent](#what-is-time-spent). This means that queries at the top are usually really slow, very frequent, or both. You can change this to sort by queries per minute to see the most frequently run queries, or by average duration to see the slowest queries. - -You can also use the dropdowns above to filter all data for specific commands (such as `SELECT` and `UPDATE`) and tables/collections queried. - -To view more details, click on a query from the table to open its **Query Summary** page. - -### Query Parameterization - -Sometimes, Sentry processes queries and simplifies them to improve readability. For example, for SQL queries: - -- Table names are removed from column selections if possible (e.g., `SELECT "users"."name", "users"."id", "users.age" FROM users` becomes `SELECT name, id, age FROM users`) -- Long lists of `SELECT` arguments are collapsed (e.g., `SELECT id, name, age, city, country, phone FROM users` becomes `SELECT .. FROM users`) -- Long lists of `VALUES` arguments are collapsed (e.g., `INSERT INTO users (id, email, name, age) VALUES (%s %s %s %s)` becomes `INSERT INTO users (..) VALUES (%s)`) -- `CASE / WHEN` statements are collapsed - -For MongoDB queries: - -- Leaf values are replaced with the placeholder `"?"` -- A maximum depth is applied to deeply nested query objects - -You can see the full query by hovering on a truncated description, or clicking it to see its **Query Summary** page. - -## Query Summary Page - -To open a query's **Query Summary** page, click on the query from either the table in the "Most Time-Consuming Queries" widget on the **Performance** page or the table in the **Queries** page. - -At the top of the page, queries per minute, average duration, and time spent are shown for the selected time range. The full query is shown below these metrics, followed by graphs for queries per minute and average duration. The query's source in the code is also shown if it is available. - -At the bottom, you can find a list of endpoints the query is found in, sorted by the most time your application spent in that span. - -If you want to investigate a specific endpoint, click on it to open a sidebar showing some sample events. - -## Query Sources - - - -Query Sources are currently supported in Sentry's [Laravel](/platforms/php/guides/laravel/configuration/laravel-options/#more-configuration) (enabled by default) and [Python](/platforms/python/configuration/options/#enable-db-query-source) (enabled by default) SDKs. Sentry only attaches query sources to queries that are slower than a configurable threshold ([Python](/platforms/python/configuration/options/#db-query-source-threshold-ms), [Laravel](/platforms/php/guides/laravel/configuration/laravel-options/#more-configuration)) to reduce the performance impact. - - - -A query's source is the location in your application's code that triggered the query. Sentry automatically determines the query source by examining the [stack trace](/product/sentry-basics/integrate-frontend/upload-source-maps/) and attaches the source to the query data. - -You can see the query's source underneath the query description on the **Query Summary** page, as shown in the image below. If you have a [source code management integration](/integrations/source-code-mgmt/) enabled, Sentry will also show a link to open the query's source in the relevant repository. - -![Example of Query Source](../img/query-source-laravel.png) - -## Sample List - -Click on an endpoint to open its samples list. This side panel shows summary metrics (QPM and average duration) for the query in the specific endpoint. - -The table shows a sample list of events, their span duration, and the difference in duration compared to the average. This table is sorted by longest span duration. - -Sentry automatically finds a variety of samples to help you investigate performance problems. The chosen events will cover the entire selected time range, as well as a range of durations (both faster than, slower than, and near the average duration). You can get a sense of the performance characteristics by comparing different sample events. - -These same events are also represented as triangles shown in the average duration graph above. - -You can generate a new list of random sample events by clicking the "Try Different Samples" button at the bottom. - -From the sample list, you can drill down to specific good, average, or bad examples of a given query within a given endpoint. Click on an event ID to drill into the query's span details within the span waterfall of the [Trace View page](/concepts/key-terms/tracing/trace-view/). - -## What is Time Spent? - -By default, queries are sorted by **time spent**, which serves as a proxy for the relative impact of a given query. - -Every database query takes some time to execute. When an application sends a query, it waits for the database to receive the query, parse it, execute it, and return the result. In Sentry, the total time taken from sending the query to receiving the full result is called the query's **duration**. The query's **time spent** is the sum of all its durations in a given period. - -For example, an application might send a query like `SELECT * FROM users LIMIT 10` every time a user calls the `/users` endpoint. The query might take anywhere from 100ms to 200ms to run, and the endpoint is called anywhere from 10 times a minute to 100 times in a minute depending on the time of day. The query's time spent is the sum of all of its durations that occurred in a given period. Put another way, the time spent is the product of the average duration and queries per minute. In a high-throughput application, a query's time spent might be measured in weeks or months. - -Time spent is a useful way to measure a query's relative impact, compared to other queries in an application. For example, if one query's time spent is 7 days, and another is just 2 hours, the query with more time spent is probably more impactful to fix. Even a small improvement in duration would result in a meaningful overall improvement. Time spent can also be a strong signal that something is wrong. Queries that suddenly start taking up more time often signal a problem. diff --git a/docs/product/insights/backend/queue-monitoring/index.mdx b/docs/product/insights/backend/queue-monitoring/index.mdx deleted file mode 100644 index 12643b5513c02..0000000000000 --- a/docs/product/insights/backend/queue-monitoring/index.mdx +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: "Queues" -sidebar_order: 30 -description: "Learn how to monitor your queues with Sentry for improved application performance and health. " ---- - - - -Insights is going away soon. You can find all the same insights over in [Sentry Dashboards](/product/dashboards/sentry-dashboards). - - - -Message Queues make asynchronous service-to-service communication possible in distributed architectures. Queues are great for making work that sometimes fails, more resilient and are therefore a building block for distributed applications. Some examples of what queues can help with include handling webhooks from third-party APIs or handling periodic tasks (such as calculating metrics for your users daily). - -If you have performance monitoring enabled and your application interacts with message queue systems, you can configure Sentry to monitor their performance and health. - -Queues allows you to monitor both the performance and error rates of your queue consumers and producers, providing observability into your distributed system. - -The **Queues** page gives you a high-level overview so that you can see where messages are being written to. (You may see topic names or actual queue names, depending on the messaging system.) If you click on a transaction, you'll see the **Destination Summary** page, which provides metrics about specific endpoints within your applications that either write to, or read from the destination. You can also dig into individual endpoints within your application representing producers creating messages, and consumers reading messages. You'll see actual traces representing messages processed by your application. - - - -### Prerequisites and Limitations - -Queues currently supports [auto instrumentation](/platform-redirect/?next=%2Ftracing%2Finstrumentation%2Fautomatic-instrumentation) for the [Celery Distributed Task Queue](https://docs.celeryq.dev/en/stable/) in Python. Other messaging systems can be monitored using custom instrumentation. - -Instructions for custom instrumentation in various languages are linked to below: - -- [Python SDK](/platforms/python/tracing/instrumentation/custom-instrumentation/queues-module/) -- [JavaScript SDK](/platforms/javascript/guides/node/tracing/instrumentation/custom-instrumentation/queues-module/) -- [PHP SDK](/platforms/php/tracing/instrumentation/queues-module/) -- [Java SDK](/platforms/java/tracing/instrumentation/custom-instrumentation/queues-module/) -- [Ruby SDK](/platforms/ruby/tracing/instrumentation/custom-instrumentation/queues-module/) -- [.NET SDK](/platforms/dotnet/tracing/instrumentation/custom-instrumentation/queues-module/) diff --git a/docs/product/insights/backend/queue-monitoring/queues-page.mdx b/docs/product/insights/backend/queue-monitoring/queues-page.mdx deleted file mode 100644 index e5ee2ad3154d3..0000000000000 --- a/docs/product/insights/backend/queue-monitoring/queues-page.mdx +++ /dev/null @@ -1,54 +0,0 @@ ---- -title: "Queues Page" -sidebar_order: 20 -description: "Learn how to use Sentry's Queues page to get an overview of queue performance and investigate potential problems. " ---- - - - -Insights is going away soon. You can find all the same insights over in [Sentry Dashboards](/product/dashboards/sentry-dashboards). - - - -The **Queues** page provides a breakdown of queue performance by destination (the topic name or queue name). Use it as a starting point to investigate potential problems with queues, such as higher than expected processing latency. - -A the top of the page, the Average Latency graph shows the total time that messages take to complete. The Published versus Processed graph shows how many messages are being written to the queue versus how many are being completed. If you see an anomaly or want to investigate a time range further, click and drag to select a range directly in the graph and you'll see data for that specific time range only. - -The destination table shows where messages are being published to, along with: - -- Throughput (the time spent both waiting and being processed in the queue) -- Error rate (how often do jobs fail to complete) -- Published versus processed count -- Time spent (total time your application spent processing jobs) - -If you want to dig deeper into the behavior of a specific destination, click the destination name to view the **Destination Summary** page. - -## Destination Summary Page - -To view the **Destination Summary** page click a [destination](https://opentelemetry.io/docs/specs/semconv/messaging/messaging-spans/#destinations) in the **Queues** page. - -At the top of the page you'll see average time in queue, average processing latency, error rate, published versus processed counts, and the total time spent by your application processing jobs. These metrics are shown in relation to the destination, whereas the **Queues** page shows summed up metrics across all destinations. Below the summary you can view graphs for average latency and published versus processed counts. - -At the bottom of the page, a table is shown listing transactions that either published or processed queue messages. - -If a problem with a specific endpoint jumps out at you, click the transaction to view sample spans and to navigate to the corresponding trace. - -### Sample List - -Click on an endpoint to open a list of sample spans. This side panel varies depending on whether you click on a producer (your application writing messages to the queue) or consumer transaction. - -### Producer Sample List - -Sentry automatically finds a variety of samples to help you investigate performance problems. The chosen spans cover the entire selected time range, as well as a range of durations and failure statues. - -The Producer panel shows the number of messages the producer has published, the error rate (representing errors that occur while publishing the message), and the average duration of the transaction that publishes the message to the queue. - -To dig even deeper, click on a span identifier to view a detailed trace. - -### Consumer Sample List - -Sentry automatically finds a variety of samples to help you investigate performance problems. The chosen spans cover the entire selected time range, as well as a range of durations and failure statues. - -The Consumer panel shows the number of messages the consumer has processed, the error rate, the average time a message spends in a queue, and the average amount of time spent processing the message. - -To dig even deeper, click on a span identifier to view a detailed trace. diff --git a/docs/product/insights/backend/requests.mdx b/docs/product/insights/backend/requests.mdx deleted file mode 100644 index 9c5c99f254d6f..0000000000000 --- a/docs/product/insights/backend/requests.mdx +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: Outbound API Requests -sidebar_order: 10 -description: "Track the performance of your application's HTTP requests and drill into the domains serving those requests." ---- - - - -Insights is going away soon. You can find all the same insights over in [Sentry Dashboards](/product/dashboards/sentry-dashboards). - - - - diff --git a/docs/product/insights/frontend/assets.mdx b/docs/product/insights/frontend/assets.mdx deleted file mode 100644 index 4551a29d2e766..0000000000000 --- a/docs/product/insights/frontend/assets.mdx +++ /dev/null @@ -1,166 +0,0 @@ ---- -title: Assets -sidebar_order: 20 -description: >- - Learn more about browser asset performance monitoring, which allows you to - debug the performance of loading JavaScript and CSS on your frontend. -og_image: /og-images/product-insights-frontend-assets.png ---- - - - -Insights is going away soon. You can find all the same insights over in [Sentry Dashboards](/product/dashboards/sentry-dashboards). - - - -If you have performance monitoring enabled for your frontend, you can see how your browser assets are performing in Sentry. - -Starting with the [**Assets** page](#assets-page), you get a high-level overview of how your assets are doing. From there, you can drill into a specific asset's [**Asset Summary** page](#asset-summary-page) and then investigate sample events from the [Sample List](#sample-list) to better understand the context of its performance in a specific page. - - - -## Prerequisites and Limitations - -The asset pages are only available for frontend JavaScript projects with performance monitoring enabled. Currently only JavaScript, CSS, images, and certain assets that are initiated by CSS (such as fonts), are supported. - -For the best experience, we recommend enabling automatic instrumentation via the `BrowserTracing` integration for your frontend project to see asset performance data. This is supported for the following JavaScript platforms: - -- [Vanilla JavaScript](/platforms/javascript/performance/) -- [Angular](/platforms/javascript/guides/angular/performance/) -- [Astro](/platforms/javascript/guides/astro/performance/) -- [Ember](/platforms/javascript/guides/ember/performance/) -- [Gatsby](/platforms/javascript/guides/gatsby/performance/) -- [Next.js](/platforms/javascript/guides/nextjs/performance/) -- [React](/platforms/javascript/guides/react/performance/) -- [Remix](/platforms/javascript/guides/remix/performance/) -- [Svelte](/platforms/javascript/guides/svelte/performance/) -- [SvelteKit](/platforms/javascript/guides/sveltekit/performance/) -- [Vue](/platforms/javascript/guides/vue/performance/) - -### Span Eligibility - -Sentry tries to extract metrics by looking at asset-related spans. - -The JavaScript SDK automatically generates `asset` spans on `pageload` and `navigation` transactions using the browser's [Resource Timing API](https://developer.mozilla.org/en-US/docs/Web/API/Performance_API/Resource_timing). - -If you are using automatic instrumentation, asset monitoring should work without any configuration. - -If you've manually instrumented Sentry, you'll need to make sure that your spans conform to our standards for the best experience: - -- The span `op` field is prefixed with `resource` (for example, `resource.script` or `resource.css`). -- The span's `description` contains the URL of the loaded resource, which should correspond to the [PerformanceResourceTiming name field](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceEntry/name). -- The `http.response_transfer_size` span data value is set to the [total transfer size](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceResourceTiming/transferSize) of the resource. -- The `http.response_content_length` span data value is set to the [encoded body size](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceResourceTiming/encodedBodySize) of the resource. -- The `http.decoded_response_content_length` span data value is set to the [decoded body size](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceResourceTiming/decodedBodySize) of the resource. -- The `resource.render_blocking_status` span data value is set to the [render blocking status](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceResourceTiming/renderBlockingStatus) of the resource. - -Here's an example snippet of creating a resource span manually with the SDK. - -```javascript -// https://developer.mozilla.org/en-US/docs/Web/API/PerformanceResourceTiming -const resources = performance.getEntriesByType("resource"); -resources.forEach((entry) => { - const startTime = msToSec(entry.startTime); - const duration = msToSec(entry.duration); - - const span = Sentry.startInactiveSpan({ - startTimestamp: startTime, - op: entry.initiatorType - ? `resource.${entry.initiatorType}` - : "resource.other", - description: entry.name, - data: { - "http.response_transfer_size": entry.transferSize, - "http.response_content_length": entry.encodedBodySize, - "http.decoded_response_content_length": entry.decodedBodySize, - "resource.render_blocking_status": entry.renderBlockingStatus, - }, - }); - - // override end timestamp to match performance entry - span.finish(startTime + duration); -}); -``` - -## Assets Page - -The **Assets** page gives you a quick overview of your application's asset performance for the selected project(s). You can use this page as a starting point to investigate potential problem assets and drill down to better understand how various assets are affecting your app's performance. - -Open the **Assets** page by clicking "Assets" in the sidebar, under "Insights". Alternatively, the **Performance** page also surfaces the highest impact assets in the "Most Time Consuming Assets" widget. From there, you can click "View All" to open the **Assets** page. - -At the top of the page, summary graphs for requests per minute (throughput) and average duration provide high-level insight into the performance of your assets. If you see an anomaly or want to investigate a time range further, you can click and drag to select a range directly in a graph to filter data for that time range. - -The asset table below shows a list of grouped assets, along with their type, their volume (requests per min), average duration, the total time your app spent loading that asset (time spent), and [average encoded size](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceResourceTiming/encodedBodySize) of the asset. - -By default, the assets table is sorted by most time spent, which serves as a proxy for the relative performance impact of a given asset. A asset's time spent is the sum of all its durations in a given time period or, put another way, the product of its average duration and requests per minute. This means that assets at the top are usually loading really slowly, very frequently, or both. - -You can click on a column header to change how the table is sorted. Sort by requests per minute to see the most frequently loaded assets or by average duration to see the slowest-loading assets. - -You can also filter assets by domain, type, page it's found on, and whether it has render blocked. - -To view more details, click on a asset from the table to open its **Asset Summary** page. - -### What Does a Render Blocking Mean? - -A render blocking asset is one which will stop the browser from rendering anything on the screen, until the asset is fully download and processed by the browser. - -An example of this is a `