diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS index 3e6209309ccc0..b377ed520b406 100644 --- a/.github/CODEOWNERS +++ b/.github/CODEOWNERS @@ -34,7 +34,7 @@ # /src/wizard/rust/ @getsentry/owners-native # /src/docs/product/discover-queries/ @getsentry/visibility -# /src/docs/product/performance/ @getsentry/visibility +# /src/docs/product/insights/ @getsentry/insights # /src/docs/cli/dif.mdx @getsentry/owners-native diff --git a/develop-docs/application-architecture/sentry-vs-getsentry.mdx b/develop-docs/application-architecture/sentry-vs-getsentry.mdx index 9346d260f8d90..a4bd187193fe7 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/), [Performance](https://docs.sentry.io/product/performance/), [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/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/). 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 69587532d450a..4b5284db2aea8 100644 --- a/develop-docs/backend/application-domains/transaction-clustering/index.mdx +++ b/develop-docs/backend/application-domains/transaction-clustering/index.mdx @@ -11,7 +11,7 @@ In terms of technical implementation, it is similar to [Data Scrubbing](/backend ## The Problem -In our [Performance](https://docs.sentry.io/product/performance/) product, transactions are grouped by their name +In our [Insights](https://docs.sentry.io/product/insights/overview/) product, transactions are grouped by their name (the [`event.transaction`](/sdk/data-model/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. @@ -22,7 +22,7 @@ and it falls back to the raw URL (or rather, [its path component](https://en.wikipedia.org/wiki/Uniform_Resource_Identifier#Syntax)). This makes it harder for the user to extract insights from [Performance -metrics](https://docs.sentry.io/product/performance/metrics/), because instead of presenting averages, percentiles and distributions of groups of transactions that logically +metrics](https://docs.sentry.io/product/insights/overview/metrics/), because instead of presenting averages, percentiles and distributions of groups of transactions that logically belong together, we end up with a bunch of one-off transaction groups. ```URLs diff --git a/develop-docs/sdk/telemetry/traces/opentelemetry.mdx b/develop-docs/sdk/telemetry/traces/opentelemetry.mdx index acf2782be6ef7..ac9eb64e88cd4 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/performance/) 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/insights/overview/) and [OpenTelemetry's tracing spec](https://opentelemetry.io/docs/concepts/signals/traces/). ## Background diff --git a/develop-docs/self-hosted/experimental/errors-only.mdx b/develop-docs/self-hosted/experimental/errors-only.mdx index 86ffb40b010cd..20c6dafdfc097 100644 --- a/develop-docs/self-hosted/experimental/errors-only.mdx +++ b/develop-docs/self-hosted/experimental/errors-only.mdx @@ -30,7 +30,7 @@ This is our default version of self-hosted Sentry. It includes most of the featu 3. [Replays](https://docs.sentry.io/product/explore/session-replay/) 4. [Insights](https://docs.sentry.io/product/insights/) (Requests, Queries, Assets, etc) 5. [User Feedback](https://docs.sentry.io/product/user-feedback/) -6. [Performance](https://docs.sentry.io/product/performance/) +6. [Insights](https://docs.sentry.io/product/insights/) 7. [Crons](https://docs.sentry.io/product/crons/) 8. [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 062f4af3c9c70..305b4848989a5 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. -- **Performance** - 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/performance/). +- **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/). - **Alerts** - Where you can create new alert rules and manage existing ones. Learn more in the full [Alerts documentation](/product/alerts/). diff --git a/docs/concepts/key-terms/tracing/distributed-tracing.mdx b/docs/concepts/key-terms/tracing/distributed-tracing.mdx index bd9b88fc4a745..b0c386a502329 100644 --- a/docs/concepts/key-terms/tracing/distributed-tracing.mdx +++ b/docs/concepts/key-terms/tracing/distributed-tracing.mdx @@ -4,7 +4,7 @@ sidebar_order: 10 description: With distributed tracing, you can track software performance and measure throughput & latency, while seeing the impact of errors across multiple systems. --- -Distributed tracing provides a connected view of your application from frontend to backend. It helps track software performance, measure [metrics](/product/performance/metrics/) like throughput and latency, and display the impact of errors across multiple systems. This makes Sentry a more complete [performance monitoring](/product/performance/) 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/insights/overview/metrics/) 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. [Tracing](/concepts/key-terms/tracing/distributed-tracing/) in Sentry provides insights such as: @@ -76,7 +76,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/performance/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/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: ![Diagram illustrating how a trace is composed of multiple transactions, and each transaction is composed of multiple spans.](./img/diagram-transaction-trace.png) @@ -227,4 +227,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/performance/) 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/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. diff --git a/docs/concepts/search/index.mdx b/docs/concepts/search/index.mdx index 02df2924042fe..674d0653d1ab8 100644 --- a/docs/concepts/search/index.mdx +++ b/docs/concepts/search/index.mdx @@ -54,7 +54,7 @@ Here are some examples of valid comparison operator searches: -`OR` and `AND` search conditions are only available for [Discover](/product/explore/discover-queries/), [Performance](/product/performance/), and [Metric Alerts](/product/alerts-notifications/metric-alerts/). +`OR` and `AND` search conditions are only available for [Discover](/product/explore/discover-queries/), [Insights Overview](/product/insights/overview/), and [Metric Alerts](/product/alerts-notifications/metric-alerts/). diff --git a/docs/concepts/search/searchable-properties/events.mdx b/docs/concepts/search/searchable-properties/events.mdx index e85a36e59e381..1719890370c3d 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/performance/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](/product/insights/overview/metrics/#apdex) that you entered. Values must be between `0` and `1`. Higher apdex values indicate higher user satisfaction. - **Type:** number @@ -685,7 +685,7 @@ Span ID of the root span of the root transaction in the event. ### `transaction` -For [transactions](/product/performance/transaction-summary/#what-is-a-transaction), the name of the transaction. For errors, the name of the associated 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. - **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/performance/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](/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. - **Type:** number diff --git a/docs/concepts/search/searchable-properties/issues.mdx b/docs/concepts/search/searchable-properties/issues.mdx index 9e74bb50e13a6..aec60dc8afd5e 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/performance/transaction-summary/#what-is-a-transaction), the name of the transaction. For errors, the name of the associated 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. - **Type:** string diff --git a/docs/contributing/approach/product-docs/write-index.mdx b/docs/contributing/approach/product-docs/write-index.mdx index 2357ef533b8c3..4931b2feeb406 100644 --- a/docs/contributing/approach/product-docs/write-index.mdx +++ b/docs/contributing/approach/product-docs/write-index.mdx @@ -41,12 +41,12 @@ 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 [Performance monitoring](/product/performance/). +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/). - 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. - Group page sections/elements or child pages as appropriate. {/**/} -- Add headings that describe the benefit rather than the page section/element like [here](/product/performance/#analyze-performance-trends). +- Add headings that describe the benefit rather than the page section/element like [here](/product/insights/overview/#analyze-performance-trends). - Describe how this feature fits in/interacts with other parts of the application, if applicable (e.g., this page has a button that takes you Discover queries). If you use this approach, you may want to include a very high-level, one- or two-sentence description of what the page looks like as part of the WHAT/WHY section. diff --git a/docs/contributing/approach/sdk-docs/write-getting-started.mdx b/docs/contributing/approach/sdk-docs/write-getting-started.mdx index afa64c1fcc6f9..1d325203e0580 100644 --- a/docs/contributing/approach/sdk-docs/write-getting-started.mdx +++ b/docs/contributing/approach/sdk-docs/write-getting-started.mdx @@ -56,7 +56,7 @@ Add the configuration code sample to this directory: -If the SDK supports performance monitoring, add it to the list that links back into the SDK content from Product, stored in [`/docs/product/performance/getting-started.mdx`](https://github.com/getsentry/sentry-docs/blob/master/docs/product/performance/getting-started.mdx). +If the SDK supports performance monitoring, add it to the list that links back into the SDK content from Product, stored in [`/docs/product/insights/getting-started.mdx`](https://github.com/getsentry/sentry-docs/blob/master/docs/product/insights/getting-started.mdx). diff --git a/docs/organization/early-adopter-features/index.mdx b/docs/organization/early-adopter-features/index.mdx index 726119d566f92..654943d08e2ab 100644 --- a/docs/organization/early-adopter-features/index.mdx +++ b/docs/organization/early-adopter-features/index.mdx @@ -19,6 +19,6 @@ Limitations: - [Issue Views](/product/issues/issue-views/) - [Issue Status](/product/issues/states-triage/) tags -- [Span Summary](/product/performance/transaction-summary/#span-summary) +- [Span Summary](/product/insights/overview/transaction-summary/#span-summary) - [Dynamic Alerts](/product/alerts/create-alerts/metric-alert-config/#dynamic-alerts) - [New Trace Explorer With Span Metrics](/product/explore/new-trace-explorer/) diff --git a/docs/platforms/android/enriching-events/transaction-name/index.mdx b/docs/platforms/android/enriching-events/transaction-name/index.mdx index ad444c6d60148..cadfaa7e3f4f1 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 [Performance](/product/performance/) 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/insights/) 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 7bb991088e85c..c60f4193fe6ee 100644 --- a/docs/platforms/android/features/index.mdx +++ b/docs/platforms/android/features/index.mdx @@ -34,7 +34,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 2f6d1a78fc411..91c574bc5f6fb 100644 --- a/docs/platforms/android/overhead/index.mdx +++ b/docs/platforms/android/overhead/index.mdx @@ -36,7 +36,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 bc66662aa0b68..302cf6a5ae541 100644 --- a/docs/platforms/android/tracing/index.mdx +++ b/docs/platforms/android/tracing/index.mdx @@ -4,7 +4,7 @@ description: "Learn how to enable tracing in your app so you can get valuable pe sidebar_order: 4000 --- -With [tracing](/product/performance/), 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/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/). diff --git a/docs/platforms/android/tracing/instrumentation/performance-metrics.mdx b/docs/platforms/android/tracing/instrumentation/performance-metrics.mdx index 854f3707b8467..99108a14cd57b 100644 --- a/docs/platforms/android/tracing/instrumentation/performance-metrics.mdx +++ b/docs/platforms/android/tracing/instrumentation/performance-metrics.mdx @@ -10,7 +10,7 @@ Sentry's SDKs support sending performance metrics data to Sentry. These are nume ## Custom Measurements -In addition to automatic performance metrics, the SDK supports setting [custom performance measurements](/product/performance/metrics/#custom-performance-measurements) on transactions. This allows you to define measurements that are important to your application and send them to Sentry. +In addition to automatic performance metrics, the SDK supports setting [custom performance measurements](/product/insights/overview/metrics/#custom-performance-measurements) on transactions. This allows you to define measurements that are important to your application and send them to Sentry. To set a performance measurement, you need to supply the following: diff --git a/docs/platforms/apple/common/overhead/index.mdx b/docs/platforms/apple/common/overhead/index.mdx index e66b5e11a8ba3..f6c4666cedfa7 100644 --- a/docs/platforms/apple/common/overhead/index.mdx +++ b/docs/platforms/apple/common/overhead/index.mdx @@ -40,7 +40,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 7c1e231a81d95..5896433346737 100644 --- a/docs/platforms/apple/common/tracing/index.mdx +++ b/docs/platforms/apple/common/tracing/index.mdx @@ -4,7 +4,7 @@ description: "Learn how to enable tracing in your app and get valuable performan sidebar_order: 4000 --- -With [tracing](/product/performance/), 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/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/). 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/performance-metrics.mdx b/docs/platforms/apple/common/tracing/instrumentation/performance-metrics.mdx index 650a94beb5245..d3e2b57dfbd61 100644 --- a/docs/platforms/apple/common/tracing/instrumentation/performance-metrics.mdx +++ b/docs/platforms/apple/common/tracing/instrumentation/performance-metrics.mdx @@ -10,7 +10,7 @@ Sentry's SDKs support sending performance metrics data to Sentry. These are nume ## Custom Measurements -In addition to automatic performance metrics, the SDK supports setting [custom performance measurements](/product/performance/metrics/#custom-performance-measurements) on transactions. This allows you to define measurements that are important to your application and send them to Sentry. +In addition to automatic performance metrics, the SDK supports setting [custom performance measurements](/product/insights/overview/metrics/#custom-performance-measurements) on transactions. This allows you to define measurements that are important to your application and send them to Sentry. To set a performance measurement, you need to supply the following: diff --git a/docs/platforms/dart/enriching-events/transaction-name/index.mdx b/docs/platforms/dart/enriching-events/transaction-name/index.mdx index f305e84733ce3..1feba90e0313d 100644 --- a/docs/platforms/dart/enriching-events/transaction-name/index.mdx +++ b/docs/platforms/dart/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 -[Performance](/product/performance/) product, as well as annotate error events +[Insights](/product/insights/) 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/features/index.mdx b/docs/platforms/dart/features/index.mdx index 5ab38f72a7f30..6a47b7a412cf3 100644 --- a/docs/platforms/dart/features/index.mdx +++ b/docs/platforms/dart/features/index.mdx @@ -14,7 +14,7 @@ Sentry's Dart SDK enables automatic reporting of errors and exceptions, and iden - Dio Integration. - Attachments enrich 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/overhead/index.mdx b/docs/platforms/dart/overhead/index.mdx index e606475900693..79e5795e189fa 100644 --- a/docs/platforms/dart/overhead/index.mdx +++ b/docs/platforms/dart/overhead/index.mdx @@ -30,7 +30,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/tracing/index.mdx b/docs/platforms/dart/tracing/index.mdx index d0a773abd0c1a..24fbc4fbb8afd 100644 --- a/docs/platforms/dart/tracing/index.mdx +++ b/docs/platforms/dart/tracing/index.mdx @@ -4,7 +4,7 @@ description: "Learn how to enable tracing in your app and get valuable performan sidebar_order: 4000 --- -With [tracing](/product/performance/), 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/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/). diff --git a/docs/platforms/dart/tracing/instrumentation/performance-metrics.mdx b/docs/platforms/dart/tracing/instrumentation/performance-metrics.mdx index 70c5b1e97e30f..384956bc02fa4 100644 --- a/docs/platforms/dart/tracing/instrumentation/performance-metrics.mdx +++ b/docs/platforms/dart/tracing/instrumentation/performance-metrics.mdx @@ -8,7 +8,7 @@ Sentry's SDKs support sending performance metrics data to Sentry. These are nume ## Custom Measurements -In addition to automatic performance metrics, the SDK supports setting [custom performance measurements](/product/performance/metrics/#custom-performance-measurements) on transactions. This allows you to define measurements that are important to your application and send them to Sentry. +In addition to automatic performance metrics, the SDK supports setting [custom performance measurements](/product/insights/overview/metrics/#custom-performance-measurements) on transactions. This allows you to define measurements that are important to your application and send them to Sentry. To set a performance measurement, you need to supply the following: 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 f305e84733ce3..1feba90e0313d 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 -[Performance](/product/performance/) product, as well as annotate error events +[Insights](/product/insights/) 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 ab0235950858a..d9b5e828f5191 100644 --- a/docs/platforms/dotnet/common/tracing/index.mdx +++ b/docs/platforms/dotnet/common/tracing/index.mdx @@ -4,7 +4,7 @@ description: "Learn how to enable tracing in your app and discover valuable perf sidebar_order: 4000 --- -With [tracing](/product/performance/), 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/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/). diff --git a/docs/platforms/dotnet/common/tracing/instrumentation/performance-metrics.mdx b/docs/platforms/dotnet/common/tracing/instrumentation/performance-metrics.mdx index 7403fd7a0075a..7115f88f18c31 100644 --- a/docs/platforms/dotnet/common/tracing/instrumentation/performance-metrics.mdx +++ b/docs/platforms/dotnet/common/tracing/instrumentation/performance-metrics.mdx @@ -8,7 +8,7 @@ Sentry's SDKs support sending performance metrics data to Sentry. These are nume ## Custom Measurements -In addition to automatic performance metrics, the SDK supports setting [custom performance measurements](/product/performance/metrics/#custom-performance-measurements) on transactions. This allows you to define measurements that are important to your application and send them to Sentry. +In addition to automatic performance metrics, the SDK supports setting [custom performance measurements](/product/insights/overview/metrics/#custom-performance-measurements) on transactions. This allows you to define measurements that are important to your application and send them to Sentry. To set a performance measurement, you need to supply the following: diff --git a/docs/platforms/flutter/configuration/options.mdx b/docs/platforms/flutter/configuration/options.mdx index 498bf15429977..b5e0b7c23c8d6 100644 --- a/docs/platforms/flutter/configuration/options.mdx +++ b/docs/platforms/flutter/configuration/options.mdx @@ -316,7 +316,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/performance/) tracking. +Set this boolean to `false` to disable auto [tracing](/product/insights/overview/) tracking. diff --git a/docs/platforms/flutter/enriching-events/transaction-name/index.mdx b/docs/platforms/flutter/enriching-events/transaction-name/index.mdx index f305e84733ce3..1feba90e0313d 100644 --- a/docs/platforms/flutter/enriching-events/transaction-name/index.mdx +++ b/docs/platforms/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 -[Performance](/product/performance/) product, as well as annotate error events +[Insights](/product/insights/) 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/flutter/overhead/index.mdx b/docs/platforms/flutter/overhead/index.mdx index 6f24c724a51ee..f8374d203b8f4 100644 --- a/docs/platforms/flutter/overhead/index.mdx +++ b/docs/platforms/flutter/overhead/index.mdx @@ -36,7 +36,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/flutter/tracing/index.mdx b/docs/platforms/flutter/tracing/index.mdx index cb90064ed57b2..2d3ace6c3e2fa 100644 --- a/docs/platforms/flutter/tracing/index.mdx +++ b/docs/platforms/flutter/tracing/index.mdx @@ -4,7 +4,7 @@ description: "Learn how to enable tracing in your app and discover valuable perf sidebar_order: 4000 --- -With [tracing](/product/performance/), 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/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/). diff --git a/docs/platforms/flutter/tracing/instrumentation/performance-metrics.mdx b/docs/platforms/flutter/tracing/instrumentation/performance-metrics.mdx index 854f3707b8467..99108a14cd57b 100644 --- a/docs/platforms/flutter/tracing/instrumentation/performance-metrics.mdx +++ b/docs/platforms/flutter/tracing/instrumentation/performance-metrics.mdx @@ -10,7 +10,7 @@ Sentry's SDKs support sending performance metrics data to Sentry. These are nume ## Custom Measurements -In addition to automatic performance metrics, the SDK supports setting [custom performance measurements](/product/performance/metrics/#custom-performance-measurements) on transactions. This allows you to define measurements that are important to your application and send them to Sentry. +In addition to automatic performance metrics, the SDK supports setting [custom performance measurements](/product/insights/overview/metrics/#custom-performance-measurements) on transactions. This allows you to define measurements that are important to your application and send them to Sentry. To set a performance measurement, you need to supply the following: 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 2e202ccb1a9a1..e473f2ccec6f7 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 -[Performance](/product/performance/) product, as well as annotate error events +[Insights](/product/insights/) 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 910426706976b..82e80401e6266 100644 --- a/docs/platforms/go/common/tracing/index.mdx +++ b/docs/platforms/go/common/tracing/index.mdx @@ -4,7 +4,7 @@ description: "Learn how to enable tracing in your app and discover valuable perf sidebar_order: 4000 --- -With [tracing](/product/performance/), 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/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/). 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 f305e84733ce3..1feba90e0313d 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 -[Performance](/product/performance/) product, as well as annotate error events +[Insights](/product/insights/) 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 71cf9229d2245..a8c9db642ec33 100644 --- a/docs/platforms/java/common/tracing/index.mdx +++ b/docs/platforms/java/common/tracing/index.mdx @@ -8,7 +8,7 @@ supported: - java.spring --- -With [tracing](/product/performance/), 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/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/). diff --git a/docs/platforms/java/common/tracing/instrumentation/performance-metrics.mdx b/docs/platforms/java/common/tracing/instrumentation/performance-metrics.mdx index 7403fd7a0075a..7115f88f18c31 100644 --- a/docs/platforms/java/common/tracing/instrumentation/performance-metrics.mdx +++ b/docs/platforms/java/common/tracing/instrumentation/performance-metrics.mdx @@ -8,7 +8,7 @@ Sentry's SDKs support sending performance metrics data to Sentry. These are nume ## Custom Measurements -In addition to automatic performance metrics, the SDK supports setting [custom performance measurements](/product/performance/metrics/#custom-performance-measurements) on transactions. This allows you to define measurements that are important to your application and send them to Sentry. +In addition to automatic performance metrics, the SDK supports setting [custom performance measurements](/product/insights/overview/metrics/#custom-performance-measurements) on transactions. This allows you to define measurements that are important to your application and send them to Sentry. To set a performance measurement, you need to supply the following: diff --git a/docs/platforms/javascript/common/configuration/integrations/browsertracing.mdx b/docs/platforms/javascript/common/configuration/integrations/browsertracing.mdx index 6f9a5d34ac10f..03aa5e10b1cf3 100644 --- a/docs/platforms/javascript/common/configuration/integrations/browsertracing.mdx +++ b/docs/platforms/javascript/common/configuration/integrations/browsertracing.mdx @@ -27,7 +27,7 @@ This integration only works inside a browser environment. _Import name: `Sentry.browserTracingIntegration`_ -With [tracing](/product/performance/), 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/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. 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/tracing/index.mdx b/docs/platforms/javascript/common/tracing/index.mdx index 42f0793ab2013..a747d667c8f21 100644 --- a/docs/platforms/javascript/common/tracing/index.mdx +++ b/docs/platforms/javascript/common/tracing/index.mdx @@ -4,7 +4,7 @@ description: "Learn how to enable tracing in your app." sidebar_order: 4000 --- -With [tracing](/product/performance/), 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/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/). You can additionally set up Profiling to get even more detailed tracing information like stack traces and flame graphs. diff --git a/docs/platforms/javascript/common/tracing/instrumentation/performance-metrics.mdx b/docs/platforms/javascript/common/tracing/instrumentation/performance-metrics.mdx index 2549f75417eb8..6b1a9ff117f9d 100644 --- a/docs/platforms/javascript/common/tracing/instrumentation/performance-metrics.mdx +++ b/docs/platforms/javascript/common/tracing/instrumentation/performance-metrics.mdx @@ -16,7 +16,7 @@ Sentry's SDKs support sending performance metrics data to Sentry. These are nume ## Custom Measurements -In addition to automatic performance metrics, the SDK supports setting [custom performance measurements](/product/performance/metrics/#custom-performance-measurements) on transactions. This allows you to define measurements that are important to your application and send them to Sentry. +In addition to automatic performance metrics, the SDK supports setting [custom performance measurements](/product/insights/overview/metrics/#custom-performance-measurements) on transactions. This allows you to define measurements that are important to your application and send them to Sentry. To set a performance measurement, you need to supply the following: 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 cca5bf7bd0a08..f32d0b372cacb 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 -[Performance](/product/performance/) product, as well as annotate error events +[Insights](/product/insights/) 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 a8377fa5eb151..f9d59466348d2 100644 --- a/docs/platforms/native/common/tracing/index.mdx +++ b/docs/platforms/native/common/tracing/index.mdx @@ -9,7 +9,7 @@ notSupported: - native.wasm --- -With [tracing](/product/performance/), 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/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/). diff --git a/docs/platforms/php/common/tracing/index.mdx b/docs/platforms/php/common/tracing/index.mdx index 27e972ef8f3b6..482f66a8bc449 100644 --- a/docs/platforms/php/common/tracing/index.mdx +++ b/docs/platforms/php/common/tracing/index.mdx @@ -4,7 +4,7 @@ description: "Learn how to enable tracing in your app and discover valuable perf sidebar_order: 4000 --- -With [tracing](/product/performance/), 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/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/). diff --git a/docs/platforms/powershell/tracing/index.mdx b/docs/platforms/powershell/tracing/index.mdx index a0bcf61547c08..e44e781f1b779 100644 --- a/docs/platforms/powershell/tracing/index.mdx +++ b/docs/platforms/powershell/tracing/index.mdx @@ -4,7 +4,7 @@ description: "Learn how to enable tracing in your app and discover valuable perf sidebar_order: 4000 --- -With [tracing](/product/performance/), 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/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/). diff --git a/docs/platforms/powershell/tracing/instrumentation/performance-metrics.mdx b/docs/platforms/powershell/tracing/instrumentation/performance-metrics.mdx index 7403fd7a0075a..7115f88f18c31 100644 --- a/docs/platforms/powershell/tracing/instrumentation/performance-metrics.mdx +++ b/docs/platforms/powershell/tracing/instrumentation/performance-metrics.mdx @@ -8,7 +8,7 @@ Sentry's SDKs support sending performance metrics data to Sentry. These are nume ## Custom Measurements -In addition to automatic performance metrics, the SDK supports setting [custom performance measurements](/product/performance/metrics/#custom-performance-measurements) on transactions. This allows you to define measurements that are important to your application and send them to Sentry. +In addition to automatic performance metrics, the SDK supports setting [custom performance measurements](/product/insights/overview/metrics/#custom-performance-measurements) on transactions. This allows you to define measurements that are important to your application and send them to Sentry. To set a performance measurement, you need to supply the following: diff --git a/docs/platforms/python/enriching-events/transaction-name/index.mdx b/docs/platforms/python/enriching-events/transaction-name/index.mdx index 2e202ccb1a9a1..e473f2ccec6f7 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 -[Performance](/product/performance/) product, as well as annotate error events +[Insights](/product/insights/) 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/performance-metrics.mdx b/docs/platforms/python/tracing/instrumentation/performance-metrics.mdx index b661abceb71b0..3ec28c7af4f26 100644 --- a/docs/platforms/python/tracing/instrumentation/performance-metrics.mdx +++ b/docs/platforms/python/tracing/instrumentation/performance-metrics.mdx @@ -8,7 +8,7 @@ Sentry's SDKs support sending performance metrics data to Sentry. These are nume ## Custom Measurements -In addition to automatic performance metrics, the SDK supports setting [custom performance measurements](/product/performance/metrics/#custom-performance-measurements) on transactions. This allows you to define measurements that are important to your application and send them to Sentry. +In addition to automatic performance metrics, the SDK supports setting [custom performance measurements](/product/insights/overview/metrics/#custom-performance-measurements) on transactions. This allows you to define measurements that are important to your application and send them to Sentry. To set a performance measurement, you need to supply the following: diff --git a/docs/platforms/react-native/configuration/options.mdx b/docs/platforms/react-native/configuration/options.mdx index fa07d8534b82a..027ff2bc84770 100644 --- a/docs/platforms/react-native/configuration/options.mdx +++ b/docs/platforms/react-native/configuration/options.mdx @@ -326,7 +326,7 @@ Set this boolean to `true` to automatically attach all threads to all logged eve -Set this boolean to `false` to disable auto [performance monitoring](/product/performance/) tracking. +Set this boolean to `false` to disable auto [performance monitoring](/product/insights/) 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 3d4b603d5b24e..64e27fd24997f 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 -[Performance](/product/performance/) product, as well as annotate error events +[Insights](/product/insights/) 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 69426b93234b4..87d72a92a8304 100644 --- a/docs/platforms/react-native/features/index.mdx +++ b/docs/platforms/react-native/features/index.mdx @@ -16,7 +16,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 cf9fa699c097a..86dbcc85981a9 100644 --- a/docs/platforms/react-native/overhead/index.mdx +++ b/docs/platforms/react-native/overhead/index.mdx @@ -36,7 +36,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 42a3e094c2c4a..8bb8233cbd2c4 100644 --- a/docs/platforms/react-native/tracing/index.mdx +++ b/docs/platforms/react-native/tracing/index.mdx @@ -4,7 +4,7 @@ description: "Learn how to enable tracing in your app and discover valuable perf sidebar_order: 4000 --- -With [tracing](/product/performance/), 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/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/). ## Configure diff --git a/docs/platforms/react-native/tracing/instrumentation/performance-metrics.mdx b/docs/platforms/react-native/tracing/instrumentation/performance-metrics.mdx index 57947bbb1be35..2bf9fa5203420 100644 --- a/docs/platforms/react-native/tracing/instrumentation/performance-metrics.mdx +++ b/docs/platforms/react-native/tracing/instrumentation/performance-metrics.mdx @@ -13,7 +13,7 @@ The React Native SDK automatically collects the following performance metrics: ## Custom Measurements -In addition to automatic performance metrics, the SDK supports setting [custom performance measurements](/product/performance/metrics/#custom-performance-measurements) on transactions. This allows you to define measurements that are important to your application and send them to Sentry. +In addition to automatic performance metrics, the SDK supports setting [custom performance measurements](/product/insights/overview/metrics/#custom-performance-measurements) on transactions. This allows you to define measurements that are important to your application and send them to Sentry. To set a performance measurement, you need to supply the following: 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 f305e84733ce3..1feba90e0313d 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 -[Performance](/product/performance/) product, as well as annotate error events +[Insights](/product/insights/) 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 4a28c4cf82eab..057cb70d182cf 100644 --- a/docs/platforms/ruby/common/migration.mdx +++ b/docs/platforms/ruby/common/migration.mdx @@ -17,7 +17,7 @@ description: "Learn about how to migrate from the deprecated sentry-raven SDK." - **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/performance/), which you can enable if you haven't already as ([discussed here](/platforms/ruby/tracing/)). +- **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/)). - **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 5e4cfdd0613c8..75ffe82993da9 100644 --- a/docs/platforms/ruby/common/tracing/index.mdx +++ b/docs/platforms/ruby/common/tracing/index.mdx @@ -4,7 +4,7 @@ description: "Learn how to enable tracing in your app and discover valuable perf sidebar_order: 4000 --- -With [tracing](/product/performance/), 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/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/). 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 7f335560511a6..a7cfa77a5d99a 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/performance/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/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). ## Custom Instrumentation diff --git a/docs/platforms/ruby/common/tracing/instrumentation/performance-metrics.mdx b/docs/platforms/ruby/common/tracing/instrumentation/performance-metrics.mdx index 7403fd7a0075a..7115f88f18c31 100644 --- a/docs/platforms/ruby/common/tracing/instrumentation/performance-metrics.mdx +++ b/docs/platforms/ruby/common/tracing/instrumentation/performance-metrics.mdx @@ -8,7 +8,7 @@ Sentry's SDKs support sending performance metrics data to Sentry. These are nume ## Custom Measurements -In addition to automatic performance metrics, the SDK supports setting [custom performance measurements](/product/performance/metrics/#custom-performance-measurements) on transactions. This allows you to define measurements that are important to your application and send them to Sentry. +In addition to automatic performance metrics, the SDK supports setting [custom performance measurements](/product/insights/overview/metrics/#custom-performance-measurements) on transactions. This allows you to define measurements that are important to your application and send them to Sentry. To set a performance measurement, you need to supply the following: diff --git a/docs/platforms/rust/common/tracing/index.mdx b/docs/platforms/rust/common/tracing/index.mdx index 909a0e747c22a..fa4ae33cbe12e 100644 --- a/docs/platforms/rust/common/tracing/index.mdx +++ b/docs/platforms/rust/common/tracing/index.mdx @@ -4,7 +4,7 @@ description: "Learn how to enable tracing in your app and discover valuable perf sidebar_order: 4000 --- -With [tracing](/product/performance/), 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/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/). diff --git a/docs/platforms/unity/enriching-events/transaction-name/index.mdx b/docs/platforms/unity/enriching-events/transaction-name/index.mdx index f305e84733ce3..1feba90e0313d 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 -[Performance](/product/performance/) product, as well as annotate error events +[Insights](/product/insights/) 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 a0bcf61547c08..e44e781f1b779 100644 --- a/docs/platforms/unity/tracing/index.mdx +++ b/docs/platforms/unity/tracing/index.mdx @@ -4,7 +4,7 @@ description: "Learn how to enable tracing in your app and discover valuable perf sidebar_order: 4000 --- -With [tracing](/product/performance/), 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/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/). diff --git a/docs/platforms/unreal/tracing/index.mdx b/docs/platforms/unreal/tracing/index.mdx index 636a48dc72ed1..ac89be94ff12c 100644 --- a/docs/platforms/unreal/tracing/index.mdx +++ b/docs/platforms/unreal/tracing/index.mdx @@ -4,7 +4,7 @@ description: "Learn how to enable tracing in your app and discover valuable perf sidebar_order: 4000 --- -With [tracing](/product/performance/), 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/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/). diff --git a/docs/pricing/legacy-pricing.mdx b/docs/pricing/legacy-pricing.mdx index aed13326f89f6..681a3a75fd118 100644 --- a/docs/pricing/legacy-pricing.mdx +++ b/docs/pricing/legacy-pricing.mdx @@ -149,7 +149,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 [performance monitoring](/product/performance/) 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/insights/) features have the ability to choose between a shared or per-category on-demand strategy: - **Shared:** 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/alerts/alert-types.mdx b/docs/product/alerts/alert-types.mdx index 9cd377dd3c63a..80f0e36b9d5e3 100644 --- a/docs/product/alerts/alert-types.mdx +++ b/docs/product/alerts/alert-types.mdx @@ -36,7 +36,7 @@ The **Alert Details** page also includes a list of issues that triggered the ale -Metric alerts tell you when a [metric](/product/performance/metrics/) crosses a threshold set by you, like a spike in the number of errors in a project, or a change in a performance metric, such as [transaction duration](/product/performance/metrics/#latency), [Apdex](/product/performance/metrics/#apdex), [failure rate](/product/performance/metrics/#failure-rate), or [throughput](/product/performance/metrics/#throughput-total-tpm-tps). You can use [dynamic alerts](/product/alerts/create-alerts/metric-alert-config/#dynamic-alerts) to let Sentry define the threshold for you. +Metric alerts tell you when a [metric](/product/insights/overview/metrics/) crosses a threshold set by you, like a spike in the number of errors in a project, or a change in a performance metric, such as [transaction duration](/product/insights/overview/metrics/#latency), [Apdex](/product/insights/overview/metrics/#apdex), [failure rate](/product/insights/overview/metrics/#failure-rate), or [throughput](/product/insights/overview/metrics/#throughput-total-tpm-tps). You can use [dynamic alerts](/product/alerts/create-alerts/metric-alert-config/#dynamic-alerts) to let Sentry define the threshold for you. Metric alerts monitor macro-level metrics for both error and transaction events. A metric takes a set of events and computes an aggregate value using a function, such as `count()` or `avg()`, applied to the event properties over a period of time. When you create a metric alert, you can filter events by attributes and tags, which is particularly useful for aggregating across events that aren't grouped into single issues. Sentry allows a maximum of 1000 metric alerts for an organization. diff --git a/docs/product/alerts/index.mdx b/docs/product/alerts/index.mdx index 94a2131743565..7e268da89512e 100644 --- a/docs/product/alerts/index.mdx +++ b/docs/product/alerts/index.mdx @@ -24,13 +24,13 @@ You can find a full list of issue alert triggers in [Issue Alert Configuration]( ## Metric Alerts for Errors & Performance -[Metric alerts](/product/alerts/alert-types/#metric-alerts) trigger when a [metric](/product/performance/metrics/) is breached for either error or transaction events. Use metric alerts to monitor a finite and known set of metrics and components you care about, such as error frequency or performance metrics in your entire project, on important pages, or with specific tags. +[Metric alerts](/product/alerts/alert-types/#metric-alerts) trigger when a [metric](/product/insights/overview/metrics/) is breached for either error or transaction events. Use metric alerts to monitor a finite and known set of metrics and components you care about, such as error frequency or performance metrics in your entire project, on important pages, or with specific tags. Create alerts to monitor metrics, such as: - Total errors in your project -- [Latency](/product/performance/metrics/#latency): min, max, average, percentile -- [Failure rate](/product/performance/metrics/#failure-rate) +- [Latency](/product/insights/overview/metrics/#latency): min, max, average, percentile +- [Failure rate](/product/insights/overview/metrics/#failure-rate) - Crash free session or user rate for monitoring release health - Custom metrics diff --git a/docs/product/dashboards/widget-library/index.mdx b/docs/product/dashboards/widget-library/index.mdx index 5e7fdaafc5875..0b1820bf99f59 100644 --- a/docs/product/dashboards/widget-library/index.mdx +++ b/docs/product/dashboards/widget-library/index.mdx @@ -54,7 +54,7 @@ To the first query, add the search condition for satisfactory transaction durati - Search condition 1: `transaction.duration:<300` -Add another query for the tolerable condition by clicking the "Add Query" button. In this example, we're using the [Apdex](/product/performance/metrics/#apdex) definition where tolerable response times are between the satisfactory threshold and four times the satisfactory threshold: +Add another query for the tolerable condition by clicking the "Add Query" button. In this example, we're using the [Apdex](/product/insights/overview/metrics/#apdex) definition where tolerable response times are between the satisfactory threshold and four times the satisfactory threshold: - Search condition 2: `transaction.duration:<1200 AND transaction.duration:>=300` diff --git a/docs/product/explore/discover-queries/query-builder/query-equations.mdx b/docs/product/explore/discover-queries/query-builder/query-equations.mdx index 49b9a1087b7f4..af3652a4fd590 100644 --- a/docs/product/explore/discover-queries/query-builder/query-equations.mdx +++ b/docs/product/explore/discover-queries/query-builder/query-equations.mdx @@ -103,7 +103,7 @@ Get the percentage of transactions that completed within a threshold ### Calculate a custom Apdex -[Apdex](/product/performance/metrics/#apdex) is defined as `(satisfied + tolerable*0.5 + frustrated*0)/total`. If you wanted to change the the weight of tolerable to 0.2, you would create the following query and equation. +[Apdex](/product/insights/overview/metrics/#apdex) is defined as `(satisfied + tolerable*0.5 + frustrated*0)/total`. If you wanted to change the the weight of tolerable to 0.2, you would create the following query and equation. 1. Create a new query with the following four columns: - Column 1: diff --git a/docs/product/explore/metrics/index.mdx b/docs/product/explore/metrics/index.mdx index 37c153497af8b..b7680f8cf2bae 100644 --- a/docs/product/explore/metrics/index.mdx +++ b/docs/product/explore/metrics/index.mdx @@ -57,7 +57,7 @@ To maintain reasonable cardinality, use tags with a fixed or predictable set of Metrics are useful for analyzing your data in aggregate. If you have more than 10 users, is it really useful to track the number of logins for each user from each platform? Probably not. Instead, what might be more valuable is to look at a dimension like a `plan_tier` (e.g. `free`, `team`, `business`,`internal users`) to segment your login data based on user categories that are meaningful for your analysis. This approach helps limit cardinality and optimizes metric analysis. -If you really are interested in individual user actions, consider using [transactions](/product/performance/transaction-summary/#what-is-a-transaction) instead of metrics. +If you really are interested in individual user actions, consider using [transactions](/product/insights/overview/transaction-summary/#what-is-a-transaction) instead of metrics. diff --git a/docs/product/explore/profiling/getting-started.mdx b/docs/product/explore/profiling/getting-started.mdx index c050c0d5c85fd..1d4a2ba7995ba 100644 --- a/docs/product/explore/profiling/getting-started.mdx +++ b/docs/product/explore/profiling/getting-started.mdx @@ -10,7 +10,7 @@ To set up the profiling integration, use the links for supported SDKs below. Pro -Profiling depends on Sentry's performance monitoring product being enabled beforehand. To enable performance monitoring in the SDK, check out our [Performance Monitoring guide](/product/performance/getting-started/). +Profiling depends on Sentry's performance monitoring product being enabled beforehand. To enable performance monitoring in the SDK, check out our [Insights guide](/product/insights/getting-started/). diff --git a/docs/product/explore/profiling/index.mdx b/docs/product/explore/profiling/index.mdx index 8fa8033b3e7af..66af28bc88783 100644 --- a/docs/product/explore/profiling/index.mdx +++ b/docs/product/explore/profiling/index.mdx @@ -21,7 +21,7 @@ description: "Profiling offers a deeper level of visibility on top of traditiona -Sentry's profiling feature builds upon our established [Performance Monitoring](/product/performance) capabilities to provide precise code-level visibility into application execution in a production environment. Profiling provides context at a deeper level than traditional tracing, enabling you to visualize the precise details of the call stack without the need for custom instrumentation. With Profiling you can quickly identify hot paths in your code and understand potential performance bottlenecks, enabling you to build in [performance as a feature](https://blog.codinghorror.com/performance-is-a-feature/) from day one. +Sentry's profiling feature builds upon our established [Insights](/product/insights) capabilities to provide precise code-level visibility into application execution in a production environment. Profiling provides context at a deeper level than traditional tracing, enabling you to visualize the precise details of the call stack without the need for custom instrumentation. With Profiling you can quickly identify hot paths in your code and understand potential performance bottlenecks, enabling you to build in [performance as a feature](https://blog.codinghorror.com/performance-is-a-feature/) from day one. Sentry profiling supports common platforms for both Mobile and Backend applications: diff --git a/docs/product/explore/session-replay/web/index.mdx b/docs/product/explore/session-replay/web/index.mdx index 93d347e689f16..4d8d3495964b7 100644 --- a/docs/product/explore/session-replay/web/index.mdx +++ b/docs/product/explore/session-replay/web/index.mdx @@ -8,7 +8,7 @@ description: "Learn about Session Replay and its video-like reproductions of use Session Replay allows you to see video-like reproductions of user sessions which can help you understand what happened before, during, and after an error or performance issue occurred. You'll be able to gain deeper debugging context into issues so that you can reproduce and resolve problems faster without the guesswork. As you play back each session, you'll be able to see every user interaction in relation to network requests, DOM events, and console messages. It’s effectively like having [DevTools](https://developer.chrome.com/docs/devtools/overview/) active in your production user sessions. -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/performance/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](https://docs.sentry.io/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/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](https://docs.sentry.io/product/issues/issue-details/breadcrumbs/), and errors. ![Session Replay User Interface](./img/session-replay.png) diff --git a/docs/product/explore/session-replay/web/replay-details.mdx b/docs/product/explore/session-replay/web/replay-details.mdx index 3fd510d27e570..ced70ba86191f 100644 --- a/docs/product/explore/session-replay/web/replay-details.mdx +++ b/docs/product/explore/session-replay/web/replay-details.mdx @@ -13,7 +13,7 @@ Every replay has a detailed view that contains the embedded video player and ric - **Replay Player:** Video-like reproduction of a user session created from DOM snapshots. This is where you can visualize exactly what actions the user took during a user session, and how the website behaved within this specific user’s environment, including browser, latency, settings, and so on. Most importantly, you can see which actions lead to an error and take the guesswork out of debugging. - By default, the Session Replay SDK is configured to replace all text nodes and user input with asterisks (\*), and to remove media elements. See all privacy configuration options [here](/platforms/javascript/session-replay/privacy/). -* **Breadcrumbs:** The replay breadcrumbs show when key user interactions took place, specifically: user clicks (including rage and dead clicks), user inputs, [page navigations, page loads](/product/performance/transaction-summary/#what-is-a-transaction), as well as [custom breadcrumbs](/product/sentry-basics/integrate-backend/configuration-options/#breadcrumbs) set by the organization and [Web Vitals](/product/insights/web-vitals/). Web Vitals are augmented with the selector to help users identify which elements are affecting their Web Vital scores. User clicks (including rage and dead clicks), are augmented with surrounding HTML source code to help users understand which event was targeted. These breadcrumbs are synced with the replay player and will auto-scroll as the video plays. +* **Breadcrumbs:** The replay breadcrumbs show when key user interactions took place, specifically: user clicks (including rage and dead clicks), user inputs, [page navigations, page loads](/product/insights/overview/transaction-summary/#what-is-a-transaction), as well as [custom breadcrumbs](/product/sentry-basics/integrate-backend/configuration-options/#breadcrumbs) set by the organization and [Web Vitals](/product/insights/web-vitals/). Web Vitals are augmented with the selector to help users identify which elements are affecting their Web Vital scores. User clicks (including rage and dead clicks), are augmented with surrounding HTML source code to help users understand which event was targeted. These breadcrumbs are synced with the replay player and will auto-scroll as the video plays. - Some [breadcrumb types](/product/issues/issue-details/breadcrumbs/) visible in **Issue Details** are not 1:1 to the replay breadcrumbs list. The trail of events typically seen in the Issue Details page are now displayed in the Console and Network components of the **Replay Details** page. - To learn more about how custom breadcrumbs are rendered, [read the docs here](/platforms/javascript/session-replay/configuration/#custom-breadcrumbs). diff --git a/docs/product/explore/traces/index.mdx b/docs/product/explore/traces/index.mdx index 787baf89e3526..913f3ac8e2075 100644 --- a/docs/product/explore/traces/index.mdx +++ b/docs/product/explore/traces/index.mdx @@ -47,7 +47,6 @@ For a list of built-in key fields used in Sentry, check out our [Searchable Prop Trace Explorer uses sampled data. Your search results may be limited based on sampling rates and retention policies. Learn more about [sampling priorities](/organization/dynamic-sampling/). - ## Search Query Results diff --git a/docs/product/index.mdx b/docs/product/index.mdx index cb04880b166aa..c094994aa530b 100644 --- a/docs/product/index.mdx +++ b/docs/product/index.mdx @@ -36,7 +36,7 @@ Sentry [**Profiling**](/product/profiling/) provides code-level insights into yo Our performance monitoring feature helps you track application performance, measure metrics like throughput and latency, and see the impact of errors across multiple services. -- Sentry helps you discover and act on [**trends**](/product/performance/trends/) before they become a bigger problem by surfacing transactions whose performance has changed significantly over time. +- Sentry helps you discover and act on [**trends**](/product/insights/overview/trends/) before they become a bigger problem by surfacing transactions whose performance has changed significantly over time. - Sentry provides insights to help you monitor your app's performance. This includes web vitals, mobile vitals, queries, HTTP requests, and more. You can drill into event samples to investigate variations in performance. ### Release Health Monitoring diff --git a/docs/product/insights/ai/index.mdx b/docs/product/insights/ai/index.mdx index 4ea88b5ec3cb7..162b062effe40 100644 --- a/docs/product/insights/ai/index.mdx +++ b/docs/product/insights/ai/index.mdx @@ -1,6 +1,6 @@ --- title: "AI Performance" -sidebar_order: 135 +sidebar_order: 40 description: "Learn how to use Sentry's AI Performance tool to get insights into things that may be affecting your application health, including critical LLM metrics." --- diff --git a/docs/product/insights/backend/index.mdx b/docs/product/insights/backend/index.mdx index fcce1c4e0cdd4..15a1857193367 100644 --- a/docs/product/insights/backend/index.mdx +++ b/docs/product/insights/backend/index.mdx @@ -1,6 +1,6 @@ --- title: "Backend Performance" -sidebar_order: 45 +sidebar_order: 20 description: "Learn how to use Sentry's Backend Performance tool to monitor things like queries, outbound API requests, caches, and queues." --- diff --git a/docs/product/insights/backend/queries.mdx b/docs/product/insights/backend/queries.mdx index 2fdc682b7024d..bf83550af9ce8 100644 --- a/docs/product/insights/backend/queries.mdx +++ b/docs/product/insights/backend/queries.mdx @@ -6,7 +6,7 @@ description: "With Queries in Sentry, you can easily see database queries, remed -If you have [performance monitoring](/product/performance/) enabled and your application queries a database, you can see how your queries are performing in Sentry. +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. diff --git a/docs/product/insights/frontend/web-vitals/index.mdx b/docs/product/insights/frontend/web-vitals/index.mdx index 74f587f3e9127..ea84c2b963209 100644 --- a/docs/product/insights/frontend/web-vitals/index.mdx +++ b/docs/product/insights/frontend/web-vitals/index.mdx @@ -39,7 +39,11 @@ The **Page Overview** page displays a "Page Loads" chart in the right sidebar of ### Samples List -The samples list only shows page loads with web vitals and performance score. If a page load is missing a required web vital, it will not be shown in the samples list. Find out which web vitals are required in the [Browser Support](/product/performance/web-vitals/web-vitals-concepts/#browser-support) table. + The samples list only shows page loads with web vitals and performance score. + If a page load is missing a required web vital, it will not be shown in the + samples list. Find out which web vitals are required in the [Browser + Support](/product/insights/frontend/web-vitals/web-vitals-concepts/#browser-support) + table. At the center of the **Page Overview**, Web Vital p75 values and scores are displayed. Clicking a Web Vital score will open a slideout panel containing a variety of **Page Load** samples with good to poor scores. Each sample contains an **Event ID** that can be clicked to open the [Trace View](/concepts/key-terms/tracing/trace-view/#product-walkthrough-trace-details-page) page for further investigation. If there is a [Replay](/product/session-replay/) or [Profile](/product/profiling/) associated with the sample page load, links will be included in the associated table columns. @@ -53,27 +57,28 @@ At the center of the **Page Overview**, Web Vital p75 values and scores are disp **Page Loads** can have up to 4 individual **Web Vital** components that can be found on each event, while interactions contribute to **INP** (Interaction to Next Paint). The default weight and score-rating thresholds for each **Web Vital** can be found in the tables below. **Desktop Browsers**: -| Web Vital | Good (90+) | Meh (50+) | Weight | +| Web Vital | Good (90+) | Meh (50+) | Weight | | --------------------------------------------------------------- | ------------------------------------------------------ | ------------------------------------------------------ | ------ | -| [Largest Contentful Paint](/product/insights/web-vitals/web-vitals-concepts/#largest-contentful-paint-lcp) (LCP) | [1200ms](https://www.desmos.com/calculator/ejhjazajbd) | [2400ms](https://www.desmos.com/calculator/ejhjazajbd) | 30% | -| [Cumulative Layout Shift](/product/insights/web-vitals/web-vitals-concepts/#cumulative-layout-shift-cls) (CLS) | [0.1](https://www.desmos.com/calculator/irdoqfftdf) | [0.25](https://www.desmos.com/calculator/irdoqfftdf) | 15% | -| [First Contentful Paint](/product/insights/web-vitals/web-vitals-concepts/#first-contentful-paint-fcp) (FCP) | [900ms](https://www.desmos.com/calculator/gcxbiypuuh) | [1600ms](https://www.desmos.com/calculator/gcxbiypuuh) | 15% | -| [Time To First Byte](/product/insights/web-vitals/web-vitals-concepts/#time-to-first-byte-ttfb) (TTFB) | [200ms](https://www.desmos.com/calculator/ykzahw9goi) | [400ms](https://www.desmos.com/calculator/ykzahw9goi) | 10% | -| [Interaction to Next Paint](/product/insights/web-vitals/web-vitals-concepts/#interaction-to-next-paint-inp) (INP) | [200ms](https://www.desmos.com/calculator/jaqxodpx8d) | [500ms](https://www.desmos.com/calculator/jaqxodpx8d) | 30% | +| [Largest Contentful Paint](/product/insights/web-vitals/web-vitals-concepts/#largest-contentful-paint-lcp) (LCP) | [1200ms](https://www.desmos.com/calculator/ejhjazajbd) | [2400ms](https://www.desmos.com/calculator/ejhjazajbd) | 30% | +| [Cumulative Layout Shift](/product/insights/web-vitals/web-vitals-concepts/#cumulative-layout-shift-cls) (CLS) | [0.1](https://www.desmos.com/calculator/irdoqfftdf) | [0.25](https://www.desmos.com/calculator/irdoqfftdf) | 15% | +| [First Contentful Paint](/product/insights/web-vitals/web-vitals-concepts/#first-contentful-paint-fcp) (FCP) | [900ms](https://www.desmos.com/calculator/gcxbiypuuh) | [1600ms](https://www.desmos.com/calculator/gcxbiypuuh) | 15% | +| [Time To First Byte](/product/insights/web-vitals/web-vitals-concepts/#time-to-first-byte-ttfb) (TTFB) | [200ms](https://www.desmos.com/calculator/ykzahw9goi) | [400ms](https://www.desmos.com/calculator/ykzahw9goi) | 10% | +| [Interaction to Next Paint](/product/insights/web-vitals/web-vitals-concepts/#interaction-to-next-paint-inp) (INP) | [200ms](https://www.desmos.com/calculator/jaqxodpx8d) | [500ms](https://www.desmos.com/calculator/jaqxodpx8d) | 30% | **Mobile Browsers**: -| Web Vital | Good (90+) | Meh (50+) | Weight | +| Web Vital | Good (90+) | Meh (50+) | Weight | | --------------------------------------------------------------- | ------------------------------------------------------ | ------------------------------------------------------ | ------ | -| [Largest Contentful Paint](/product/insights/web-vitals/web-vitals-concepts/#largest-contentful-paint-lcp) (LCP) | [2500ms](https://www.desmos.com/calculator/tegmkln1hr) | [4000ms](https://www.desmos.com/calculator/tegmkln1hr) | 30% | -| [Cumulative Layout Shift](/product/insights/web-vitals/web-vitals-concepts/#cumulative-layout-shift-cls) (CLS) | [0.1](https://www.desmos.com/calculator/irdoqfftdf) | [0.25](https://www.desmos.com/calculator/irdoqfftdf) | 15% | -| [First Contentful Paint](/product/insights/web-vitals/web-vitals-concepts/#first-contentful-paint-fcp) (FCP) | [1800ms](https://www.desmos.com/calculator/ezkvtlqxkf) | [3000ms](https://www.desmos.com/calculator/ezkvtlqxkf) | 15% | -| [Time To First Byte](/product/insights/web-vitals/web-vitals-concepts/#time-to-first-byte-ttfb) (TTFB) | [800ms](https://www.desmos.com/calculator/xcpjhfvwfo) | [1800ms](https://www.desmos.com/calculator/xcpjhfvwfo) | 10% | -| [Interaction to Next Paint](/product/insights/web-vitals/web-vitals-concepts/#interaction-to-next-paint-inp) (INP) | [200ms](https://www.desmos.com/calculator/jaqxodpx8d) | [500ms](https://www.desmos.com/calculator/jaqxodpx8d) | 30% | +| [Largest Contentful Paint](/product/insights/web-vitals/web-vitals-concepts/#largest-contentful-paint-lcp) (LCP) | [2500ms](https://www.desmos.com/calculator/tegmkln1hr) | [4000ms](https://www.desmos.com/calculator/tegmkln1hr) | 30% | +| [Cumulative Layout Shift](/product/insights/web-vitals/web-vitals-concepts/#cumulative-layout-shift-cls) (CLS) | [0.1](https://www.desmos.com/calculator/irdoqfftdf) | [0.25](https://www.desmos.com/calculator/irdoqfftdf) | 15% | +| [First Contentful Paint](/product/insights/web-vitals/web-vitals-concepts/#first-contentful-paint-fcp) (FCP) | [1800ms](https://www.desmos.com/calculator/ezkvtlqxkf) | [3000ms](https://www.desmos.com/calculator/ezkvtlqxkf) | 15% | +| [Time To First Byte](/product/insights/web-vitals/web-vitals-concepts/#time-to-first-byte-ttfb) (TTFB) | [800ms](https://www.desmos.com/calculator/xcpjhfvwfo) | [1800ms](https://www.desmos.com/calculator/xcpjhfvwfo) | 10% | +| [Interaction to Next Paint](/product/insights/web-vitals/web-vitals-concepts/#interaction-to-next-paint-inp) (INP) | [200ms](https://www.desmos.com/calculator/jaqxodpx8d) | [500ms](https://www.desmos.com/calculator/jaqxodpx8d) | 30% | These thresholds are meant to match Google Lighthouse as closely as possible, but there may be some differences because Sentry operates on real user data, whereas Google Lighthouse operates on lab data. Some browsers may not support all **Web Vitals** used in Sentry's **Performance Score** calculation. Look at the [Browser Support](/product/insights/web-vitals/web-vitals-concepts/#browser-support) table to see which Web Vitals are supported by your browser. + ## Opportunity @@ -97,4 +102,4 @@ Although Sentry provides auto instrumentation for many frontend frameworks, ther - **Performance Scores** only support **Chrome**, **Firefox**, **Safari**, **Opera**, and **Edge** desktop and mobile browsers. - Some pageloads may not capture all web vitals supported by Sentry. This may depending on the client browser and/or the unique behavior of your web page. **Performance Score** are calculated based on available web vitals. - - Find out the full list of web vitals in the [Browser Support](/product/insights/web-vitals/web-vitals-concepts/#browser-support) table. + - Find out the full list of web vitals in the [Browser Support](/product/insights/web-vitals/web-vitals-concepts/#browser-support) table. diff --git a/docs/product/insights/frontend/web-vitals/web-vitals-concepts.mdx b/docs/product/insights/frontend/web-vitals/web-vitals-concepts.mdx index 8b1c3610adfc1..f8ec2d41c3d96 100644 --- a/docs/product/insights/frontend/web-vitals/web-vitals-concepts.mdx +++ b/docs/product/insights/frontend/web-vitals/web-vitals-concepts.mdx @@ -7,9 +7,9 @@ description: "Learn more about web vitals and how each metric relates to your ap -[Web Vitals](https://web.dev/vitals/) are a set of metrics defined by Google to measure render time, response time, and layout shift. Each data point provides insights about the overall [performance](/product/performance/) of your application. +[Web Vitals](https://web.dev/vitals/) are a set of metrics defined by Google to measure render time, response time, and layout shift. Each data point provides insights about the overall [performance](/product/insights/overview/) of your application. -The in-browser Sentry SDKs collect web vitals information (where supported) and adds that information to frontend [transactions](/product/performance/transaction-summary/). These web vitals are then summarized in the [**Performance > Web Vitals** page](/product/insights/web-vitals/) to give you a quick overview of how each page is performing for your users. +The in-browser Sentry SDKs collect web vitals information (where supported) and adds that information to frontend [transactions](/product/insights/overview/transaction-summary/). These web vitals are then summarized in the [**Performance > Web Vitals** page](/product/insights/web-vitals/) to give you a quick overview of how each page is performing for your users. ![Visualization of Web Vitals](../../img/diagram-transaction-vitals.png) diff --git a/docs/product/insights/mobile/index.mdx b/docs/product/insights/mobile/index.mdx index 7f89d78b6017d..5b91246b9e8de 100644 --- a/docs/product/insights/mobile/index.mdx +++ b/docs/product/insights/mobile/index.mdx @@ -1,6 +1,6 @@ --- title: "Mobile Performance" -sidebar_order: 90 +sidebar_order: 30 description: "Learn how to use Sentry's Mobile Performance tool to monitor the health of your mobile app, including app starts, screen loads, and screen rendering." --- diff --git a/docs/product/insights/overview/filters-display/img/01_half_widget_frontend.png b/docs/product/insights/overview/filters-display/img/01_half_widget_frontend.png new file mode 100644 index 0000000000000..4f01811aed47e Binary files /dev/null and b/docs/product/insights/overview/filters-display/img/01_half_widget_frontend.png differ diff --git a/docs/product/performance/filters-display/img/transaction-name-search.png b/docs/product/insights/overview/filters-display/img/transaction-name-search.png similarity index 100% rename from docs/product/performance/filters-display/img/transaction-name-search.png rename to docs/product/insights/overview/filters-display/img/transaction-name-search.png diff --git a/docs/product/performance/filters-display/img/widgets_average_ttids.png b/docs/product/insights/overview/filters-display/img/widgets_average_ttids.png similarity index 100% rename from docs/product/performance/filters-display/img/widgets_average_ttids.png rename to docs/product/insights/overview/filters-display/img/widgets_average_ttids.png diff --git a/docs/product/performance/filters-display/img/widgets_best_page_opportunities.png b/docs/product/insights/overview/filters-display/img/widgets_best_page_opportunities.png similarity index 100% rename from docs/product/performance/filters-display/img/widgets_best_page_opportunities.png rename to docs/product/insights/overview/filters-display/img/widgets_best_page_opportunities.png diff --git a/docs/product/performance/filters-display/img/widgets_most_frozen_frames.png b/docs/product/insights/overview/filters-display/img/widgets_most_frozen_frames.png similarity index 100% rename from docs/product/performance/filters-display/img/widgets_most_frozen_frames.png rename to docs/product/insights/overview/filters-display/img/widgets_most_frozen_frames.png diff --git a/docs/product/performance/filters-display/img/widgets_most_related_issues.png b/docs/product/insights/overview/filters-display/img/widgets_most_related_issues.png similarity index 100% rename from docs/product/performance/filters-display/img/widgets_most_related_issues.png rename to docs/product/insights/overview/filters-display/img/widgets_most_related_issues.png diff --git a/docs/product/performance/filters-display/img/widgets_most_slow_frames.png b/docs/product/insights/overview/filters-display/img/widgets_most_slow_frames.png similarity index 100% rename from docs/product/performance/filters-display/img/widgets_most_slow_frames.png rename to docs/product/insights/overview/filters-display/img/widgets_most_slow_frames.png diff --git a/docs/product/performance/filters-display/img/widgets_most_time_consuming_domains.png b/docs/product/insights/overview/filters-display/img/widgets_most_time_consuming_domains.png similarity index 100% rename from docs/product/performance/filters-display/img/widgets_most_time_consuming_domains.png rename to docs/product/insights/overview/filters-display/img/widgets_most_time_consuming_domains.png diff --git a/docs/product/performance/filters-display/img/widgets_most_time_spent_assets.png b/docs/product/insights/overview/filters-display/img/widgets_most_time_spent_assets.png similarity index 100% rename from docs/product/performance/filters-display/img/widgets_most_time_spent_assets.png rename to docs/product/insights/overview/filters-display/img/widgets_most_time_spent_assets.png diff --git a/docs/product/performance/filters-display/img/widgets_most_time_spent_queries.png b/docs/product/insights/overview/filters-display/img/widgets_most_time_spent_queries.png similarity index 100% rename from docs/product/performance/filters-display/img/widgets_most_time_spent_queries.png rename to docs/product/insights/overview/filters-display/img/widgets_most_time_spent_queries.png diff --git a/docs/product/performance/filters-display/img/widgets_performance_score.png b/docs/product/insights/overview/filters-display/img/widgets_performance_score.png similarity index 100% rename from docs/product/performance/filters-display/img/widgets_performance_score.png rename to docs/product/insights/overview/filters-display/img/widgets_performance_score.png diff --git a/docs/product/performance/filters-display/img/widgets_slow_db_ops.png b/docs/product/insights/overview/filters-display/img/widgets_slow_db_ops.png similarity index 100% rename from docs/product/performance/filters-display/img/widgets_slow_db_ops.png rename to docs/product/insights/overview/filters-display/img/widgets_slow_db_ops.png diff --git a/docs/product/performance/filters-display/img/widgets_slow_http_ops.png b/docs/product/insights/overview/filters-display/img/widgets_slow_http_ops.png similarity index 100% rename from docs/product/performance/filters-display/img/widgets_slow_http_ops.png rename to docs/product/insights/overview/filters-display/img/widgets_slow_http_ops.png diff --git a/docs/product/performance/filters-display/img/widgets_slow_resource_ops.png b/docs/product/insights/overview/filters-display/img/widgets_slow_resource_ops.png similarity index 100% rename from docs/product/performance/filters-display/img/widgets_slow_resource_ops.png rename to docs/product/insights/overview/filters-display/img/widgets_slow_resource_ops.png diff --git a/docs/product/performance/filters-display/index.mdx b/docs/product/insights/overview/filters-display/index.mdx similarity index 62% rename from docs/product/performance/filters-display/index.mdx rename to docs/product/insights/overview/filters-display/index.mdx index 30724979a1ee4..3bc20df1a2775 100644 --- a/docs/product/performance/filters-display/index.mdx +++ b/docs/product/insights/overview/filters-display/index.mdx @@ -1,20 +1,14 @@ --- title: "Filters & Display" sidebar_order: 20 -description: "Manage the information on the Performance page using search or page-level display filters to quickly identify performance issues." +description: "Manage the information on the Insight Overview page using search or page-level display filters to quickly identify performance issues." --- You can filter the information displayed on the **Performance** page by searching or using page-level display filters. ## Transaction and Trend Views -The page displays a view of transactions, but you can click the “View Trends” button to view trends information. The different ways you can filter and set the display of transactions is described fully on this page. To learn more about viewing transactions by trend, see our [Trends View documentation](/product/performance/trends/). - -## Tabs - -Each tab in **Performance** displays an automatically selected set of [widgets](#widgets) and table columns based on the platform of your project. For example, a JavaScript project displays the "Web Vitals" tab by default. Each tab and its [metrics](/product/performance/metrics/) are explained below. - -![Performance homepage with Web Vitals tab selected.](./img/01_full_widget_frontend.png) +The page displays a view of transactions, but you can click the “View Trends” button to view trends information. The different ways you can filter and set the display of transactions is described fully on this page. To learn more about viewing transactions by trend, see our [Trends View documentation](/product/insights/overview/trends/). ### All Transactions @@ -55,7 +49,7 @@ In the transaction summary, the search bar operates similarly to the one in the ## Widgets -[Widgets](/product/performance/filters-display/widgets/) offer visualizations that you can change to best match your workflow. +[Widgets](/product/insights/overview/filters-display/widgets/) offer visualizations that you can change to best match your workflow. ![Performance homepage with Web Vitals widgets.](./img/01_half_widget_frontend.png) @@ -67,31 +61,27 @@ Each widget has a menu in the top right where can you change the widget shown. Y ### Basic Widgets -- [Apdex](/product/performance/metrics/#apdex) -- [Transactions Per Minute (TPM)](/product/performance/metrics/#throughput-total-tpm-tps) -- [Failure Rate](/product/performance/metrics/#failure-rate) -- [p50 Duration](/product/performance/metrics/#p50-threshold) -- [p75 Duration](/product/performance/metrics/#p75-threshold) -- [p95 Duration](/product/performance/metrics/#p95-threshold) -- [p99 Duration](/product/performance/metrics/#p99-threshold) -- [User Misery](/product/performance/metrics/#user-misery) +- [Apdex](/product/insights/overview/metrics/#apdex) +- [Transactions Per Minute (TPM)](/product/insights/overview/metrics/#throughput-total-tpm-tps) +- [Failure Rate](/product/insights/overview/metrics/#failure-rate) +- [p50 Duration](/product/insights/overview/metrics/#p50-threshold) +- [p75 Duration](/product/insights/overview/metrics/#p75-threshold) +- [p95 Duration](/product/insights/overview/metrics/#p95-threshold) +- [p99 Duration](/product/insights/overview/metrics/#p99-threshold) +- [User Misery](/product/insights/overview/metrics/#user-misery) ### Actionable Widgets -- [Most Improved](/product/performance/filters-display/widgets/#most-improved) -- [Most Regressed](/product/performance/filters-display/widgets/#most-regressed) -- [Most Related Issues](/product/performance/filters-display/widgets/#most-related-issues) -- [Most Slow Frames](/product/performance/filters-display/widgets/#most-slow-frames) -- [Most Frozen Frames](/product/performance/filters-display/widgets/#most-frozen-frames) -- [Most Time-Consuming Queries](/product/performance/filters-display/widgets/#most-time-consuming-queries) -- [Most Time-Consuming Assets](/product/performance/filters-display/widgets/#most-time-consuming-assets) -- [Most Time-Consuming Domains](/product/performance/filters-display/widgets/#most-time-consuming-domains) -- [Best Page Opportunities](/product/performance/filters-display/widgets/#best-page-opportunities) -- [Performance Score](/product/performance/filters-display/widgets/#performance-score) -- [Slow HTTP Ops](/product/performance/filters-display/widgets/#slow-http-ops) -- [Slow DB Ops](/product/performance/filters-display/widgets/#slow-db-ops) -- [Slow Browser Ops](/product/performance/filters-display/widgets/#slow-browser-ops) -- [Slow Resource Ops](/product/performance/filters-display/widgets/#slow-resource-ops) +- [Most Slow Frames](/product/insights/overview/filters-display/widgets/#most-slow-frames) +- [Most Frozen Frames](/product/insights/overview/filters-display/widgets/#most-frozen-frames) +- [Most Time-Consuming Queries](/product/insights/overview/filters-display/widgets/#most-time-consuming-queries) +- [Most Time-Consuming Assets](/product/insights/overview/filters-display/widgets/#most-time-consuming-assets) +- [Most Time-Consuming Domains](/product/insights/overview/filters-display/widgets/#most-time-consuming-domains) +- [Best Page Opportunities](/product/insights/overview/filters-display/widgets/#best-page-opportunities) +- [Slow HTTP Ops](/product/insights/overview/filters-display/widgets/#slow-http-ops) +- [Slow DB Ops](/product/insights/overview/filters-display/widgets/#slow-db-ops) +- [Slow Browser Ops](/product/insights/overview/filters-display/widgets/#slow-browser-ops) +- [Slow Resource Ops](/product/insights/overview/filters-display/widgets/#slow-resource-ops) ## Transaction Table @@ -101,14 +91,14 @@ The [Display Filter](#display-filter) controls what displays in the table column - Transaction Name - Project - Operation -- [TPM](/product/performance/metrics/#throughput-total-tpm-tps) -- [P50](/product/performance/metrics/#average-transaction-duration) -- [P95](/product/performance/metrics/#p95-threshold) -- [Failure Rate](/product/performance/metrics/#failure-rate) -- [Apdex](/product/performance/metrics/#apdex) +- [TPM](/product/insights/overview/metrics/#throughput-total-tpm-tps) +- [P50](/product/insights/overview/metrics/#average-transaction-duration) +- [P95](/product/insights/overview/metrics/#p95-threshold) +- [Failure Rate](/product/insights/overview/metrics/#failure-rate) +- [Apdex](/product/insights/overview/metrics/#apdex) - Unique Users -- [User Misery](/product/performance/metrics/#user-misery) +- [User Misery](/product/insights/overview/metrics/#user-misery) ### Starring Key Transactions -If you have transactions you frequently return to, you can mark them as a key transaction for any of your teams by clicking the star in the corresponding row. Each team can mark up to 100 transactions as a key transaction. These key transactions are shared with all members of the team ensuring the most important information is surfaced to the top of the list. You can also mark a transaction as a key transaction in its corresponding [summary view](/product/performance/transaction-summary/#starring-key-transactions). +If you have transactions you frequently return to, you can mark them as a key transaction for any of your teams by clicking the star in the corresponding row. Each team can mark up to 100 transactions as a key transaction. These key transactions are shared with all members of the team ensuring the most important information is surfaced to the top of the list. You can also mark a transaction as a key transaction in its corresponding [summary view](/product/insights/overview/transaction-summary/#starring-key-transactions). diff --git a/docs/product/performance/filters-display/widgets.mdx b/docs/product/insights/overview/filters-display/widgets.mdx similarity index 51% rename from docs/product/performance/filters-display/widgets.mdx rename to docs/product/insights/overview/filters-display/widgets.mdx index bc5dfbe261ff4..68d5c0449835b 100644 --- a/docs/product/performance/filters-display/widgets.mdx +++ b/docs/product/insights/overview/filters-display/widgets.mdx @@ -1,15 +1,15 @@ --- -title: "Performance Widgets" +title: "Widgets" sidebar_order: 10 -description: "Learn more about Sentry's Performance widgets such as Most Related Issues, Most Regressed Transactions, and Slow HTTP Ops, and how they can be used to surface performance insights in your applications." +description: "Learn more about Sentry's Insights widgets such as Most Slow Frames, Most Time-Consuming Queries, and Slow HTTP Ops, and how they can be used to surface performance insights in your applications." --- -Performance widgets offer visualizations that you can change to best match your workflow. They provide performance-specific views that allow you to see and act on transaction data across your organization. -Depending on which [Performance Tab](/product/performance/filters-display/#tabs) you've selected, different curated performance widgets will be available. +Insights widgets offer visualizations that you can change to best match your workflow. They provide performance-specific views that allow you to see and act on transaction data across your organization. +Depending on which [Insight Domain](http://localhost:3000/product/insights/) you've selected, different curated performance widgets will be available. -The value displayed in the top right of some widgets is the **overall value for the selected time period**, not the average of the data displayed in the chart. For datasets with low event volume, the overall value may be higher or lower than expected because metrics like [Apdex](/product/performance/metrics/#apdex) and [User Misery](/product/performance/metrics/#user-misery) are non-linear. +The value displayed in the top right of some widgets is the **overall value for the selected time period**, not the average of the data displayed in the chart. For datasets with low event volume, the overall value may be higher or lower than expected because metrics like [Apdex](/product/insights/overview/metrics/#apdex) and [User Misery](/product/insights/overview/metrics/#user-misery) are non-linear. @@ -17,33 +17,15 @@ The value displayed in the top right of some widgets is the **overall value for Shows the average TTID duration for top screens for mobile projects. Click the screen name to view more information about the screen in the [Screen Loads](/product/insights/mobile-vitals/screen-loads/) page. -This widget is available in the [Mobile](/product/performance/filters-display/#mobile) tab. +This widget is available in the [Mobile Overview](/product/insights/mobile/). ![Performance Widgets - Average TTIDs](./img/widgets_average_ttids.png) -## Most Changed - -Shows those transactions from the selected transaction list that have changed (either improved or regressed) the most. Note that only trends of a specific significance and throughput are shown and that precedence is given to the most regressed transactions. - -To filter by either **Most Improved** or **Most Regressed**, navigate to the trends page using the **View Trends** button. Learn more in [Trends](/product/performance/trends). - -This widget is available in the [All Transactions](/product/performance/filters-display/#all-transactions), [Backend](/product/performance/filters-display/#backend) and [Mobile](/product/performance/filters-display/#mobile) tabs. - -![Performance Widgets - Most Changed](./img/widgets_most_changed.png) - -## Most Related Issues - -Shows the highest count of any issue group related to a transaction and visualizes the issue count over time. - -This widget is available in the [All Transactions](/product/performance/filters-display/#all-transactions) tab. - -![Performance Widgets - Most Related Issues](./img/widgets_most_related_issues.png) - ## Most Slow Frames Shows transactions with the most slow frames for mobile projects. Learn more in [Mobile Vitals](/product/insights/mobile-vitals). -This widget is available in the [Mobile](/product/performance/filters-display/#mobile) tab. +This widget is available in the [Mobile Overview](/product/insights/mobile/). ![Performance Widgets - Most Slow Frames](./img/widgets_most_slow_frames.png) @@ -51,7 +33,7 @@ This widget is available in the [Mobile](/product/performance/filters-display/#m Shows transactions with the most frozen frames for mobile projects. Learn more in [Mobile Vitals](/product/insights/mobile-vitals). -This widget is available in the [Mobile](/product/performance/filters-display/#mobile) tab. +This widget is available in the [Mobile Overview](/product/insights/mobile) tab. ![Performance Widgets - Most Frozen Frames](./img/widgets_most_frozen_frames.png) @@ -59,15 +41,15 @@ This widget is available in the [Mobile](/product/performance/filters-display/#m Shows database queries that take the most time in your application. These queries are usually either slow, very frequent, or both. Click on a query to open its [**Query Summary** page](/product/insights/queries#query-summary-page) or click "View All" to open the [**Queries** page](/product/insights/queries#queries-page). -This widget is available in the [All Transactions](/product/performance/filters-display/#all-transactions) and [Backend](/product/performance/filters-display/#backend) tabs. +This widget is available in the [Backend Overview](/product/insights/backend/). ![Performance Widgets - Most Time Spent Queries](./img/widgets_most_time_spent_queries.png) ## Most Time-Consuming Assets -Shows assets that take the most time in your application. These assets are usually either slow, very frequent, or both. Click on a asset to open its [**Asset Summary** page](/product/insights/assets#asset-summary-page) or click "View All" to open the [**Assets** page](/product/insights/assets#assets-page). +Shows assets that take the most time in your application. These assets are usually either slow, very frequent, or both. Click on a asset to open its [**Asset Summary** page](/product/insights/frontend/assets#asset-summary-page) or click "View All" to open the [**Assets** page](/product/insights/frontend/assets#assets-page). -This widget is available in the [Frontend](/product/performance/filters-display/#frontend) tab. +This widget is available in the [Frontend Overview](/product/insights/frontend/). ![Performance Widgets - Most Time Spent Assets](./img/widgets_most_time_spent_assets.png) @@ -75,7 +57,7 @@ This widget is available in the [Frontend](/product/performance/filters-display/ Shows domains that the application spends a lot of time waiting for, sorted by total time per domain. The application either makes a lot of calls to these domains, or these domains take a long time to respond to requests. Click on a domain to open its [**Domain Summary** page](/product/insights/requests#domain-summary-page) or click "View All" to open the [**Requests** page](/product/insights/requests#requests-page). -This widget is available in the [All Transactions](/product/performance/filters-display/#all-transactions), [Backend](/product/performance/filters-display/#backend), [Frontend](/product/performance/filters-display/#frontend) and [Mobile](/product/performance/filters-display/#mobile) tabs. +This widget is available in the [Backend Overview](/product/insights/backend/), [Frontend Overview](/product/insights/frontend/) and [Mobile Overview](/product/insights/mobile/) tabs. ![Performance Widgets - Most time-consuming domains](./img/widgets_most_time_consuming_domains.png) @@ -83,23 +65,15 @@ This widget is available in the [All Transactions](/product/performance/filters- Shows web pages in your application that have the most [Opportunity](/product/insights/web-vitals/#opportunity) to improve. These pages usually have poor [Web Vital](/product/insights/web-vitals/) scores, high throughput, or both. Click on a page to open its [**Page Overview** page](/product/insights/web-vitals/#page-overview) or click "View All" to open the [**Web Vitals** page](/product/insights/web-vitals/#web-vitals-page). -This widget is available in the [Frontend](/product/performance/filters-display/#frontend) tab. +This widget is available in the [Frontend Overview](/product/insights/frontend/). ![Performance Widgets - Best Page Opportunities](./img/widgets_best_page_opportunities.png) -## Performance Score - -Shows the [Performance Score](/product/insights/web-vitals/#performance-score) breakdown of your web projects. Click on a Web Vital component or "View All" to open a summary in the [**Web Vitals** page](/product/insights/web-vitals/#web-vitals-page). - -This widget is available in the [All Transactions](/product/performance/filters-display/#all-transactions) tab. - -![Performance Widgets - Performance Score](./img/widgets_performance_score.png) - ## Slow HTTP Ops Shows transactions with slow cumulative HTTP spans. Slow HTTP ops are not shown for all projects and transactions as the transactions must contain HTTP spans. Check out the SDK documentation for the project in question for more information. -This widget is available in the [Frontend](/product/performance/filters-display/#frontend) and [Backend](/product/performance/filters-display/#backend) tabs. +This widget is available in the [Frontend Overview](/product/insights/frontend/) and [Backend Overview](/product/insights/backend/) tabs. ![Performance Widgets - Slow HTTP Ops](./img/widgets_slow_http_ops.png) @@ -107,7 +81,7 @@ This widget is available in the [Frontend](/product/performance/filters-display/ Shows transactions with slow cumulative DB spans. Slow DB ops are not shown for all projects and transactions as the transactions must contain DB spans. Check out the SDK documentation for the project in question for more information. -This widget is available in the [Backend](/product/performance/filters-display/#backend) tab. +This widget is available in the [Backend Overview](/product/insights/backend/). ![Performance Widgets - Slow HTTP Ops](./img/widgets_slow_db_ops.png) @@ -115,6 +89,6 @@ This widget is available in the [Backend](/product/performance/filters-display/# Shows transactions with slow cumulative resource spans. These show frontend transactions with poor performing resources spans, and show cumulative time spent loading scripts, CSS, and so on. -This widget is available in the [Frontend](/product/performance/filters-display/#frontend) tab. +This widget is available in the [Frontend Overview](/product/insights/frontend/). ![Performance Widgets - Slow Resource Ops](./img/widgets_slow_resource_ops.png) diff --git a/docs/product/insights/overview/img/01_full_widget_all.png b/docs/product/insights/overview/img/01_full_widget_all.png new file mode 100644 index 0000000000000..ef0cc5f868287 Binary files /dev/null and b/docs/product/insights/overview/img/01_full_widget_all.png differ diff --git a/docs/product/performance/img/custom-metrics-performance.png b/docs/product/insights/overview/img/custom-metrics-performance.png similarity index 100% rename from docs/product/performance/img/custom-metrics-performance.png rename to docs/product/insights/overview/img/custom-metrics-performance.png diff --git a/docs/product/performance/img/exclusive-time.png b/docs/product/insights/overview/img/exclusive-time.png similarity index 100% rename from docs/product/performance/img/exclusive-time.png rename to docs/product/insights/overview/img/exclusive-time.png diff --git a/docs/product/insights/overview/img/perf-transaction-summary.png b/docs/product/insights/overview/img/perf-transaction-summary.png new file mode 100644 index 0000000000000..a00ce6c470cb2 Binary files /dev/null and b/docs/product/insights/overview/img/perf-transaction-summary.png differ diff --git a/docs/product/performance/img/resource-sample-images.png b/docs/product/insights/overview/img/resource-sample-images.png similarity index 100% rename from docs/product/performance/img/resource-sample-images.png rename to docs/product/insights/overview/img/resource-sample-images.png diff --git a/docs/product/performance/img/tags-tab.png b/docs/product/insights/overview/img/tags-tab.png similarity index 100% rename from docs/product/performance/img/tags-tab.png rename to docs/product/insights/overview/img/tags-tab.png diff --git a/docs/product/performance/img/transaction-trace-detail.png b/docs/product/insights/overview/img/transaction-trace-detail.png similarity index 100% rename from docs/product/performance/img/transaction-trace-detail.png rename to docs/product/insights/overview/img/transaction-trace-detail.png diff --git a/docs/product/insights/overview/img/trends.png b/docs/product/insights/overview/img/trends.png new file mode 100644 index 0000000000000..92980a1df937c Binary files /dev/null and b/docs/product/insights/overview/img/trends.png differ diff --git a/docs/product/insights/overview/index.mdx b/docs/product/insights/overview/index.mdx new file mode 100644 index 0000000000000..646f5f37aae17 --- /dev/null +++ b/docs/product/insights/overview/index.mdx @@ -0,0 +1,53 @@ +--- +title: "Overview" +sidebar_order: 50 +description: "With insights, you can track, analyze, and debug your application's performance. Sentry helps you identify performance opportunities and trace issues back to poorly performing code." +--- + +With insights, Sentry tracks application performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple services. Sentry captures [distributed traces](/product/sentry-basics/tracing/distributed-tracing/) consisting of [transactions](/product/insights/overview/transaction-summary/#what-is-a-transaction) and spans to measure individual services and operations within those services. + + + +Learn more about traces in the [full Tracing documentation](/product/sentry-basics/tracing/). + + + +The **Insights Overview** page is the main view in [sentry.io](https://sentry.io) where you can search or browse for transaction data. A transaction represents a single instance of an activity you want to measure or track, such as a page load, page navigation, or an asynchronous task. The page displays graphs that visualize transactions or [trends](/product/insights/overview/trends/), as well as a table where you can view relevant transactions and drill down to get more information about them. + +![Performance homepage with All Transactions tab selected.](./img/01_full_widget_all.png) + +Using the information on this page, you can trace issues back through services (for instance, frontend to backend) to identify poorly performing code. You'll be able to determine whether your application performance is getting better or worse, see if your last release is running more slowly than previous ones, and identify specific services that are slow. Once you've found the cause of the problem, you'll be able to address the specific code that’s degrading performance. + +## Filter Performance Data + +The **Insights Overview** page provides you with several filter and display options so that you can focus on the performance data that's most important to you. You can use the project, environment, and date filters to customize the information displayed on the page, including what's shown in the [widgets](/product/insights/overview/filters-display/#widgets) and [transactions table](/product/insights/overview/filters-display/#transaction-table). You can also search to find and filter for the specific transactions you want to investigate. + +## Analyze Performance Trends + +The [trends view](/product/insights/overview/trends/) allows you to see transactions that have had significant performance changes over time. This view is ideal for insights about transactions with large counts. + +## Investigate Transactions + +When you find a transaction of interest, you can investigate further by going to its [Transaction Summary page](/product/insights/overview/transaction-summary). Every transaction has a summary view that gives you a better understanding of its overall health. With this view, you'll find graphs, instances of these events, stats, facet maps, related errors, and more. + +The summary page for Frontend transactions links out to the web vitals page, where you can see a detailed view of the [Web Vitals](/product/insights/web-vitals/) associated with the transaction. You can also access a **Transaction Summary** page from the transactions table on the **Performance** page. + +## Explore Performance Metrics + +There are several types of [metrics](/product/insights/overview/metrics/) that you can visualize in the graphs, such as Apdex, Transactions Per Minute, P50 Duration, and User Misery to get a full understanding of how your software is performing. + +## Triage Performance Issues + + + +**Issue and Event Quotas** + +Your quota is consumed by events or traces, not issues. Performance issues are generated from your accepted transactions, which **doesn't** directly impact your quota. Insight transaction events use transactions, which **does** directly impact your quota. Sentry provides tools to control the type and number of error and transaction events that are accepted. Learn more in [Quota Management](/pricing/quotas/manage-transaction-quota). + + + +If your application is configured for Insights and Tracing, Sentry will detect common performance problems, and group them into issues just like it does with errors. Performance issues help to surface performance problems in your application and provide a workflow for resolving them. Learn more about [performance issues](/product/issues/issue-details/performance-issues/). + +## Learn More + + diff --git a/docs/product/performance/metrics.mdx b/docs/product/insights/overview/metrics.mdx similarity index 94% rename from docs/product/performance/metrics.mdx rename to docs/product/insights/overview/metrics.mdx index a127ff81bab8c..b69be3afcfdcd 100644 --- a/docs/product/performance/metrics.mdx +++ b/docs/product/insights/overview/metrics.mdx @@ -4,7 +4,7 @@ sidebar_order: 110 description: "Learn more about Sentry's Performance metrics such as Apdex, failure rate, throughput, and latency, and the user experience insights about your application that they provide." --- -Metrics provide insight about how users are experiencing your application. In [Performance](/product/performance/), we'll set you up with a few of the basic metrics to get you started. For further customizations on target thresholds, feel free to build out a query using the Discover [Query Builder](/product/explore/discover-queries/query-builder/). By identifying useful thresholds to measure your application, you have a quantifiable measurement of your application's health. This means you can more easily identify when errors occur or if performance issues are emerging. +Metrics provide insight about how users are experiencing your application. In [Insights](/product/insights/overview/), we'll set you up with a few of the basic metrics to get you started. For further customizations on target thresholds, feel free to build out a query using the Discover [Query Builder](/product/explore/discover-queries/query-builder/). By identifying useful thresholds to measure your application, you have a quantifiable measurement of your application's health. This means you can more easily identify when errors occur or if performance issues are emerging. ## Apdex diff --git a/docs/product/performance/transaction-summary.mdx b/docs/product/insights/overview/transaction-summary.mdx similarity index 71% rename from docs/product/performance/transaction-summary.mdx rename to docs/product/insights/overview/transaction-summary.mdx index c3b272bf7765e..a1d3c2962aea0 100644 --- a/docs/product/performance/transaction-summary.mdx +++ b/docs/product/insights/overview/transaction-summary.mdx @@ -12,7 +12,7 @@ Every transaction has a summary view that gives you a better understanding of it A transaction represents a single instance of an activity you want to measure or track, like a page load, page navigation, or an asynchronous task. Having transaction information lets you monitor the overall performance of your application beyond when it crashes or generates an error. Without transactions, you can only know when things in your application have actually gone wrong, which is important, but not the whole picture. -Transactions on the **Performance** page are grouped by the transaction names, such as endpoint paths for backend request transactions (like `/store/checkout/` or `api/v2/users//`) or URLs/routes for page load transactions (like `https://docs.sentry.io/performance-monitoring/`). When you click a transaction on the **Performance** page, it takes you to the **Transaction Summary**, where you can see a list of transaction events: that is, the individual instances of that specific transaction. +Transactions on the **Insights Overview** page are grouped by the transaction names, such as endpoint paths for backend request transactions (like `/store/checkout/` or `api/v2/users//`) or URLs/routes for page load transactions (like `https://docs.sentry.io/product/insights/`). When you click a transaction on the **Insights Overview** page, it takes you to the **Transaction Summary**, where you can see a list of transaction events: that is, the individual instances of that specific transaction. @@ -30,17 +30,17 @@ While you can use the search field to narrow down your events, you can also filt ### Graphs -- **Duration Breakdown:** By graphing [P50](/product/performance/metrics/#p50-threshold), [P75](/product/performance/metrics/#p75-threshold), [P95](/product/performance/metrics/#p95-threshold), [P99](/product/performance/metrics/#p99-threshold), and P100 durations distinctly, you can utilize this display to see their transaction performance over time. Toggle the display of each segment by clicking on the legend (including Releases). Also, zoom in on specific slices to investigate spikes or possible performance regressions from a release. +- **Duration Breakdown:** By graphing [P50](/product/insights/overview/metrics/#p50-threshold), [P75](/product/insights/overview/metrics/#p75-threshold), [P95](/product/insights/overview/metrics/#p95-threshold), [P99](/product/insights/overview/metrics/#p99-threshold), and P100 durations distinctly, you can utilize this display to see their transaction performance over time. Toggle the display of each segment by clicking on the legend (including Releases). Also, zoom in on specific slices to investigate spikes or possible performance regressions from a release. -- **Duration Percentiles:** This graph shows the [average transaction duration](/product/performance/metrics/#average-transaction-duration) across distinct percentiles. For example, see how different the P50 and P99 response time durations are for a given transaction and understand the rate of increase between segments. +- **Duration Percentiles:** This graph shows the [average transaction duration](/product/insights/overview/metrics/#average-transaction-duration) across distinct percentiles. For example, see how different the P50 and P99 response time durations are for a given transaction and understand the rate of increase between segments. - **Duration Distribution:** This graph shows the volume of transactions per median duration. This view helps you understand the spread of the transaction durations in order to determine the likelihood of different outcomes. For example, what transaction duration is the most likely for a user. - **Trends:** This graph uses a modified version of [ASAP](https://arxiv.org/pdf/1703.00983.pdf) smoothing. The Trends graph shows the unsmoothed data of the Display data, along with a smoothed version of that data. -- **Web Vitals:** This graph displays the [P75 threshold](/product/performance/metrics/#p75-threshold) of [First Paint](/product/insights/web-vitals/web-vitals-concepts/#first-paint-fp), [First Contentful Paint](/product/insights/web-vitals/web-vitals-concepts/#first-contentful-paint-fcp), [Largest Contentful Paint](/product/insights/web-vitals/web-vitals-concepts/#largest-contentful-paint-lcp), and [First Input Delay](/product/insights/web-vitals/web-vitals-concepts/#first-input-delay-fid) over time. This view helps you understand how the Web Vitals associated with the transaction are performing over time. +- **Web Vitals:** This graph displays the [P75 threshold](/product/insights/overview/metrics/#p75-threshold) of [First Paint](/product/insights/web-vitals/web-vitals-concepts/#first-paint-fp), [First Contentful Paint](/product/insights/web-vitals/web-vitals-concepts/#first-contentful-paint-fcp), [Largest Contentful Paint](/product/insights/web-vitals/web-vitals-concepts/#largest-contentful-paint-lcp), and [First Input Delay](/product/insights/web-vitals/web-vitals-concepts/#first-input-delay-fid) over time. This view helps you understand how the Web Vitals associated with the transaction are performing over time. -- **User Misery:** This graph displays the [User Misery](/product/performance/metrics/#user-misery) score for the transaction. User Misery is a score that represents the number of unique users who have experienced load times four times the project's configured threshold. +- **User Misery:** This graph displays the [User Misery](/product/insights/overview/metrics/#user-misery) score for the transaction. User Misery is a score that represents the number of unique users who have experienced load times four times the project's configured threshold. ### Transaction Table @@ -83,25 +83,7 @@ This table will show you all related issues. In other words, any errors that are ### Sidebar -The sidebar contains helpful supplementary information about this transaction's [User Misery](/product/performance/metrics/#user-misery), [Apdex](/product/performance/metrics/#apdex), [Throughput](/product/performance/metrics/#throughput-total-tpm-tps), [Latency](/product/performance/metrics/#latency), and more. You'll also find a Tag Summary (facet map) for a list of common tags related to this transaction. - -## Web Vitals - -Frontend transactions will have a "Web Vitals" tab. Clicking on the tab will take you to the distribution histogram of web vitals for that transaction. To drill further into your application's web vitals, you can also go to the [Web Vitals page](/product/insights/web-vitals). - -### Distribution Histogram - -![Example of Web Vitals](./img/perf-web-vitals.png) - -The Web Vitals histogram displays data distribution, and it can help you identify and diagnose frontend performance problems by revealing anomalies. - -By default, outliers will be excluded from the histograms to provide a more informative view of these vitals. Outliers are determined using the [upper outer fence](https://en.wikipedia.org/wiki/Outlier#Tukey's_fences) as the upper bound, and any data points above the upper bound are deemed an outlier. - -The vertical marker for each Web Vital is the 75th percentile of the observed data points. In other words, 25% of the recorded values exceed that amount. - -If you notice a region of interest on any of the histograms, click and drag over the area to zoom in for a more detailed view. You may also want to see more information related to the transactions in the histograms. Click "Open in Discover" beneath the Web Vital of choice to build a custom query for further investigation. For more details, see the full documentation for the Discover [Query Builder](/product/explore/discover-queries/query-builder/). - -If you wish to see all of the data available, open the dropdown and click "View All". You will likely see extreme outliers when you click "View All". You can click and drag over an area to zoom in for a more detailed view. +The sidebar contains helpful supplementary information about this transaction's [User Misery](/product/insights/overview/metrics/#user-misery), [Apdex](/product/insights/overview/metrics/#apdex), [Throughput](/product/insights/overview/metrics/#throughput-total-tpm-tps), [Latency](/product/insights/overview/metrics/#latency), and more. You'll also find a Tag Summary (facet map) for a list of common tags related to this transaction. ## Tags @@ -163,7 +145,7 @@ The Replays tab displays a list of replays where the transaction you’re viewin ### Starring Important Transactions -If you find an important transaction you want to return to, click "Star for Team" in the upper right corner to mark it as a key transaction for any of your teams. This will be saved so you can view this from your [Performance Homepage](/product/performance/). The transactions you star will be shared with members of the same team and each team can have up to 100 starred transactions. +If you find an important transaction you want to return to, click "Star for Team" in the upper right corner to mark it as a key transaction for any of your teams. This will be saved so you can view this from your [Insights Overview Homepage](/product/insights/overview/). The transactions you star will be shared with members of the same team and each team can have up to 100 starred transactions. ### Creating Alerts diff --git a/docs/product/performance/trends.mdx b/docs/product/insights/overview/trends.mdx similarity index 65% rename from docs/product/performance/trends.mdx rename to docs/product/insights/overview/trends.mdx index 1f6314f0adc55..926d0912bb5cf 100644 --- a/docs/product/performance/trends.mdx +++ b/docs/product/insights/overview/trends.mdx @@ -8,10 +8,10 @@ From the Performance homepage, you can find the Trends View by toggling the tab ![trends Homepage](./img/trends.png) -Trending transactions are calculated first by filtering out transactions with large [throughput](/product/performance/metrics/#throughput-total-tpm-tps) fluctuations, determining the baselines of the two halves of the duration, and calculating their percentage change. Regressions are any percentage changes greater than zero, while improvements are percentage changes less than zero. +Trending transactions are calculated first by filtering out transactions with large [throughput](/product/insights/overview/metrics/#throughput-total-tpm-tps) fluctuations, determining the baselines of the two halves of the duration, and calculating their percentage change. Regressions are any percentage changes greater than zero, while improvements are percentage changes less than zero. Sentry uses a [t-test](https://academic.oup.com/beheco/article/17/4/688/215960) to compare the before and after periods of the transaction and assign a confidence score. -For example, looking at a transaction over two weeks with the default [P50](/product/performance/metrics/#average-transaction-duration) baseline, if the first week had a `p(50)=100s`, and the second a `p(50)=110s`, the percentage is `(110/100)-1 = 0.1`. The example transaction had a performance regression of `10%`. +For example, looking at a transaction over two weeks with the default [P50](/product/insights/overview/metrics/#average-transaction-duration) baseline, if the first week had a `p(50)=100s`, and the second a `p(50)=110s`, the percentage is `(110/100)-1 = 0.1`. The example transaction had a performance regression of `10%`. The more data is available, the more the accuracy of the trend improves. For this reason, trends perform best over long periods and with transactions with large counts. diff --git a/docs/product/performance/performance-overhead.mdx b/docs/product/insights/performance-overhead.mdx similarity index 79% rename from docs/product/performance/performance-overhead.mdx rename to docs/product/insights/performance-overhead.mdx index f0d9b4c6a50de..382bc8feba5fb 100644 --- a/docs/product/performance/performance-overhead.mdx +++ b/docs/product/insights/performance-overhead.mdx @@ -1,12 +1,12 @@ --- title: Performance Overhead -sidebar_order: 120 -description: "Learn more about how enabling Performance Monitoring in Sentry impacts the performance of your application." +sidebar_order: 3 +description: "Learn more about how enabling Insights and Tracing in Sentry impacts the performance of your application." --- -Enabling performance in Sentry SDKs adds some overhead, but should have minimal impact on the performance of your application. +Enabling insights and tracing in Sentry SDKs adds some overhead, but should have minimal impact on the performance of your application. -Performance monitoring works by instrumenting important parts of typical applications such as: +They work by instrumenting important parts of typical applications such as: - Database calls - Incoming and outgoing HTTP requests @@ -15,13 +15,13 @@ Performance monitoring works by instrumenting important parts of typical applica - Component lifecycle in UI frameworks - Web Vitals -To perform this instrumentation, Sentry SDKs wrap or monkeypatch specific functions within popular libraries or frameworks and measure the execution time of these operations. These are then packaged and serialized into a payload containing a [Transaction](/product/performance/transaction-summary/#what-is-a-transaction) (containing Spans) that is transmitted to event ingestion servers via the internet. +To perform this instrumentation, Sentry SDKs wrap or monkeypatch specific functions within popular libraries or frameworks and measure the execution time of these operations. These are then packaged and serialized into a payload containing a [Transaction](/product/insights/overview/transaction-summary/#what-is-a-transaction) (containing Spans) that is transmitted to event ingestion servers via the internet. The SDKs also make sure to propagate some headers on outgoing requests so that [Distributed Tracing](/product/sentry-basics/tracing/) can work effectively. -For most applications, the performance overhead of enabling performance in production is imperceptible to end users. +For most applications, the performance overhead of enabling insights and tracing in production is imperceptible to end users. diff --git a/docs/product/issues/issue-details/performance-issues/endpoint-regressions/index.mdx b/docs/product/issues/issue-details/performance-issues/endpoint-regressions/index.mdx index 6285f04db7b56..5778a575b3984 100644 --- a/docs/product/issues/issue-details/performance-issues/endpoint-regressions/index.mdx +++ b/docs/product/issues/issue-details/performance-issues/endpoint-regressions/index.mdx @@ -37,7 +37,7 @@ The below chart shows the p95 transaction duration over a period of up to 14 day The "Potential Causes" section shows a list of spans that may have contributed to the slowdown the most. Next to each span, you'll find the following: -- Span description that leads to the [Span Summary](/product/performance/transaction-summary/) page where you can find more information about that specific span. +- Span description that leads to the [Span Summary](/product/insights/overview/transaction-summary/) page where you can find more information about that specific span. - P95 of span self time before the regression. - P95 of span self time after the regression. - The percentage change in p95 span self time before and after the regression. diff --git a/docs/product/issues/issue-details/performance-issues/index.mdx b/docs/product/issues/issue-details/performance-issues/index.mdx index aabad22262f9c..2c40ec94e1eeb 100644 --- a/docs/product/issues/issue-details/performance-issues/index.mdx +++ b/docs/product/issues/issue-details/performance-issues/index.mdx @@ -4,7 +4,7 @@ sidebar_order: 20 description: "Learn more about which performance issues Sentry detects and how to use the Issue Details page to debug them." --- -A _performance issue_ is a grouping of transaction events that are performing poorly. If your application is configured for [Performance Monitoring](/product/performance/), Sentry will detect common performance problems, and group them into issues. We group similar transaction events into issues based on a fingerprint. For performance issues, a fingerprint is primarily based on the problem type and the spans involved in the problem. +A _performance issue_ is a grouping of transaction events that are performing poorly. If your application is configured for [Insights and Tracing](/product/insights/), Sentry will detect common performance problems, and group them into issues. We group similar transaction events into issues based on a fingerprint. For performance issues, a fingerprint is primarily based on the problem type and the spans involved in the problem. The **Issue Details** page helps you to gain further insight into the source of a performance issue and the impact it has on your application's users. The main area of the page displays information about a specific transaction event that's part of an issue. The top panel and right-hand sidebar of the page display a summary of all the transaction events grouped together in this issue: diff --git a/docs/product/performance/filters-display/img/01_full_widget_frontend.png b/docs/product/performance/filters-display/img/01_full_widget_frontend.png deleted file mode 100644 index 5a978587a9d42..0000000000000 Binary files a/docs/product/performance/filters-display/img/01_full_widget_frontend.png and /dev/null differ diff --git a/docs/product/performance/filters-display/img/01_half_widget_frontend.png b/docs/product/performance/filters-display/img/01_half_widget_frontend.png deleted file mode 100644 index a1510c9c0acd5..0000000000000 Binary files a/docs/product/performance/filters-display/img/01_half_widget_frontend.png and /dev/null differ diff --git a/docs/product/performance/filters-display/img/widgets_most_changed.png b/docs/product/performance/filters-display/img/widgets_most_changed.png deleted file mode 100644 index 0785907b0514a..0000000000000 Binary files a/docs/product/performance/filters-display/img/widgets_most_changed.png and /dev/null differ diff --git a/docs/product/performance/getting-started.mdx b/docs/product/performance/getting-started.mdx deleted file mode 100644 index c1061339a3918..0000000000000 --- a/docs/product/performance/getting-started.mdx +++ /dev/null @@ -1,106 +0,0 @@ ---- -title: Set Up -sidebar_order: 1 -description: "Get started with Sentry's Performance Monitoring, which allows you to see macro-level metrics to micro-level spans, cross-reference transactions with related issues, and customize queries." ---- - -If you don't already have performance monitoring enabled, use the links for supported SDKs below to quickly set up access to our [Performance Monitoring](/product/performance/) features. Performance Monitoring helps you see everything from macro-level [metrics](/product/performance/metrics/) to micro-level [spans](/concepts/key-terms/tracing/trace-view/#product-walkthrough-trace-view-page), and you'll be able to cross-reference [transactions with related issues](/product/performance/transaction-summary/), customize [queries](/product/explore/discover-queries/query-builder/) based on your personal needs, and substantially more. - -## Supported SDKs - -- - - - [ASP.NET Core](/platforms/dotnet/guides/aspnetcore/tracing/) - - [OpenTelemetry](/platforms/dotnet/tracing/instrumentation/opentelemetry/) - -- - - - [Echo](/platforms/go/guides/echo/performance/) - - [FastHTTP](/platforms/go/guides/fasthttp/performance/) - - [Fiber](/platforms/go/guides/fiber/performance/) - - [Gin](/platforms/go/guides/gin/performance/) - - [Iris](/platforms/go/guides/iris/performance/) - - [Negroni](/platforms/go/guides/negroni/performance/) - - [net/http](/platforms/go/guides/http/performance/) - - [OpenTelemetry](/platforms/go/performance/instrumentation/opentelemetry/) - -- - - - [OpenTelemetry](/platforms/java/tracing/instrumentation/opentelemetry/) - - [Spring](/platforms/java/guides/spring/tracing/) - - [Spring Boot](/platforms/java/guides/spring-boot/tracing/) - -- - - - [Angular](/platforms/javascript/guides/angular/tracing/) - - [Astro](/platforms/javascript/guides/astro/tracing/) - - [AWS Lambda](/platforms/javascript/guides/aws-lambda/tracing/) - - [Azure Functions](/platforms/javascript/guides/azure-functions/tracing/) - - [Bun](/platforms/javascript/guides/bun/tracing/) - - [Connect](/platforms/javascript/guides/connect/tracing/) - - [Deno](/platforms/javascript/guides/deno/tracing/) - - [Electron](/platforms/javascript/guides/electron/tracing/) - - [Ember](/platforms/javascript/guides/ember/tracing/) - - [Express](/platforms/javascript/guides/express/tracing/) - - [Fastify](/platforms/javascript/guides/fastify/tracing/) - - [Gatsby](/platforms/javascript/guides/gatsby/tracing/) - - [Google Cloud Functions](/platforms/javascript/guides/gcp-functions/tracing/) - - [Hapi](/platforms/javascript/guides/hapi/tracing/) - - [Hono](/platforms/javascript/guides/hono/tracing/) - - [Koa](/platforms/javascript/guides/koa/tracing/) - - [Nest.js](/platforms/javascript/guides/nestjs/tracing/) - - [Next.js](/platforms/javascript/guides/nextjs/tracing/) - - [Node.js](/platforms/javascript/guides/node/tracing/) - - [OpenTelemetry](/platforms/javascript/guides/node/tracing/instrumentation/opentelemetry/) - - [React](/platforms/javascript/guides/react/tracing/) - - [Remix](/platforms/javascript/guides/remix/tracing/) - - [Solid](/platforms/javascript/guides/solid/tracing/) - - [Svelte](/platforms/javascript/guides/svelte/tracing/) - - [SvelteKit](/platforms/javascript/guides/sveltekit/tracing/) - - [Vue](/platforms/javascript/guides/vue/tracing/) - -- - -- - -- - -- - -- - -- - - - [OpenTelemetry](/platforms/python/tracing/instrumentation/opentelemetry/) - -- - - - [Laravel](/platforms/php/guides/laravel/tracing/) - - [Symfony](/platforms/php/guides/symfony/tracing/) - -- - - - [DelayedJob](/platforms/ruby/guides/delayed_job/tracing/) - - [OpenTelemetry](/platforms/ruby/tracing/instrumentation/opentelemetry/) - - [Rails](/platforms/ruby/guides/rails/tracing/) - - [Resque](/platforms/ruby/guides/resque/tracing/) - - [Sidekiq](/platforms/ruby/guides/sidekiq/tracing/) - -- - -- diff --git a/docs/product/performance/img/01_full_widget_all.png b/docs/product/performance/img/01_full_widget_all.png deleted file mode 100644 index 75edd3f453482..0000000000000 Binary files a/docs/product/performance/img/01_full_widget_all.png and /dev/null differ diff --git a/docs/product/performance/img/perf-transaction-summary.png b/docs/product/performance/img/perf-transaction-summary.png deleted file mode 100644 index c87f1a91a79d2..0000000000000 Binary files a/docs/product/performance/img/perf-transaction-summary.png and /dev/null differ diff --git a/docs/product/performance/img/perf-web-vitals.png b/docs/product/performance/img/perf-web-vitals.png deleted file mode 100644 index 9bd1d747ae979..0000000000000 Binary files a/docs/product/performance/img/perf-web-vitals.png and /dev/null differ diff --git a/docs/product/performance/img/trends.png b/docs/product/performance/img/trends.png deleted file mode 100644 index 401a14833a080..0000000000000 Binary files a/docs/product/performance/img/trends.png and /dev/null differ diff --git a/docs/product/projects/project-details/index.mdx b/docs/product/projects/project-details/index.mdx index 1ca0aad709d08..07ee66d356483 100644 --- a/docs/product/projects/project-details/index.mdx +++ b/docs/product/projects/project-details/index.mdx @@ -11,7 +11,7 @@ The top four cards display the following: - Crash free [sessions](/product/releases/health/#session) - Crash free users - Number of [releases](/product/releases/) -- [Apdex](/product/performance/metrics/#apdex) +- [Apdex](/product/insights/overview/metrics/#apdex) The two graphs below the cards show the value of a specific metric over the specified time range. Click on the graph legend to show or hide an overlay of the previous time period and any releases (if set up). @@ -23,9 +23,9 @@ By default, the graphs show crash free sessions and Apdex, but you can toggle th - Crash free [sessions](/product/releases/health/#session) - Crash free users -- [Apdex](/product/performance/metrics/#apdex) -- [Failure rate](/product/performance/metrics/#failure-rate) -- [Transactions per minute](/product/performance/metrics/#throughput-total-tpm-tps) +- [Apdex](/product/insights/overview/metrics/#apdex) +- [Failure rate](/product/insights/overview/metrics/#failure-rate) +- [Transactions per minute](/product/insights/overview/metrics/#throughput-total-tpm-tps) - Number of errors - Number of sessions - Number of transactions diff --git a/docs/product/releases/release-details.mdx b/docs/product/releases/release-details.mdx index 81e847a16b550..78d2638cb68bc 100644 --- a/docs/product/releases/release-details.mdx +++ b/docs/product/releases/release-details.mdx @@ -17,7 +17,7 @@ The graph at the top of the page provides insights into the health of your relea - [Crash Free User Rate](/product/releases/health/#crash-free-sessionsusers) - Crashed Session Rate - [Crashed User Rate](/product/releases/health/#crashed-users) -- [Failure Rate](/product/performance/metrics/#failure-rate) +- [Failure Rate](/product/insights/overview/metrics/#failure-rate) - [Session Count](/product/releases/health/#session) - Error Count - Transaction Count diff --git a/docs/product/sentry-basics/integrate-frontend/configure-scms.mdx b/docs/product/sentry-basics/integrate-frontend/configure-scms.mdx index 578750ce07a77..8f66e3de8177f 100644 --- a/docs/product/sentry-basics/integrate-frontend/configure-scms.mdx +++ b/docs/product/sentry-basics/integrate-frontend/configure-scms.mdx @@ -178,7 +178,7 @@ You should now have Sentry's error monitoring set up with source maps and suspec On top of error monitoring, Sentry offers other features to help you detect and fix problems with your apps, like: - [Session Replay](/product/explore/session-replay/) to view a a video-like reproduction of your user sessions when errors occur. -- [Performance Monitoring](/product/performance/) to track application performance and errors across services. +- [Insights](/product/insights/) to track application performance and errors across services. - [Profiling](/product/explore/profiling/) to get deeper level of visibility on top of traditional tracing. As well as [Codecov](https://docs.codecov.com/docs) to give you automated code coverage reports as part of your CI/CD. diff --git a/docs/product/performance/index.mdx b/docs/product/sentry-basics/performance-monitoring.mdx similarity index 67% rename from docs/product/performance/index.mdx rename to docs/product/sentry-basics/performance-monitoring.mdx index eec381abc50bf..c5136c59ba238 100644 --- a/docs/product/performance/index.mdx +++ b/docs/product/sentry-basics/performance-monitoring.mdx @@ -6,7 +6,7 @@ description: "With performance monitoring, you can track, analyze, and debug you -With performance monitoring, Sentry tracks application performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple services. Sentry captures [distributed traces](/product/sentry-basics/tracing/distributed-tracing/) consisting of [transactions](/product/performance/transaction-summary/#what-is-a-transaction) and spans to measure individual services and operations within those services. +With performance monitoring, Sentry tracks application performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple services. Sentry captures [distributed traces](/product/sentry-basics/tracing/distributed-tracing/) consisting of [transactions](/product/insights/overview/transaction-summary/#what-is-a-transaction) and spans to measure individual services and operations within those services. @@ -14,29 +14,29 @@ Learn more about traces in the [full Tracing documentation](/product/sentry-basi -The **Performance** page is the main view in [sentry.io](https://sentry.io) where you can search or browse for transaction data. A transaction represents a single instance of an activity you want to measure or track, such as a page load, page navigation, or an asynchronous task. The page displays graphs that visualize transactions or [trends](/product/performance/trends/), as well as a table where you can view relevant transactions and drill down to get more information about them. +The **Performance** page is the main view in [sentry.io](https://sentry.io) where you can search or browse for transaction data. A transaction represents a single instance of an activity you want to measure or track, such as a page load, page navigation, or an asynchronous task. The page displays graphs that visualize transactions or [trends](/product/insights/overview/trends/), as well as a table where you can view relevant transactions and drill down to get more information about them. -![Performance homepage with All Transactions tab selected.](./img/01_full_widget_all.png) +![Insights Overview Page](../../product/insights/img/backend-performance-overview.png) Using the information on this page, you can trace issues back through services (for instance, frontend to backend) to identify poorly performing code. You'll be able to determine whether your application performance is getting better or worse, see if your last release is running more slowly than previous ones, and identify specific services that are slow. Once you've found the cause of the problem, you'll be able to address the specific code that’s degrading performance. ## Filter Performance Data -The **Performance** page provides you with several filter and display options so that you can focus on the performance data that's most important to you. You can use the project, environment, and date filters to customize the information displayed on the page, including what's shown in the [widgets](/product/performance/filters-display/#widgets) and [transactions table](/product/performance/filters-display/#transaction-table). You can also search to find and filter for the specific transactions you want to investigate. +The **Performance** page provides you with several filter and display options so that you can focus on the performance data that's most important to you. You can use the project, environment, and date filters to customize the information displayed on the page, including what's shown in the [widgets](/product/insights/overview/filters-display/#widgets) and [transactions table](/product/insights/overview/filters-display/#transaction-table). You can also search to find and filter for the specific transactions you want to investigate. ## Analyze Performance Trends -The [trends view](/product/performance/trends/) allows you to see transactions that have had significant performance changes over time. This view is ideal for insights about transactions with large counts. +The [trends view](/product/insights/overview/trends/) allows you to see transactions that have had significant performance changes over time. This view is ideal for insights about transactions with large counts. ## Investigate Transactions -When you find a transaction of interest, you can investigate further by going to its [Transaction Summary page](/product/performance/transaction-summary). Every transaction has a summary view that gives you a better understanding of its overall health. With this view, you'll find graphs, instances of these events, stats, facet maps, related errors, and more. +When you find a transaction of interest, you can investigate further by going to its [Transaction Summary page](/product/insights/overview/transaction-summary). Every transaction has a summary view that gives you a better understanding of its overall health. With this view, you'll find graphs, instances of these events, stats, facet maps, related errors, and more. The summary page for Frontend transactions has a "Web Vitals" tab, where you can see a detailed view of the [Web Vitals](/product/insights/web-vitals/) associated with the transaction. You can also access a **Transaction Summary** page from the transactions table on the **Performance** page. ## Explore Performance Metrics -There are several types of [metrics](/product/performance/metrics/) that you can visualize in the graphs, such as Apdex, Transactions Per Minute, P50 Duration, and User Misery to get a full understanding of how your software is performing. +There are several types of [metrics](/product/insights/overview/metrics/) that you can visualize in the graphs, such as Apdex, Transactions Per Minute, P50 Duration, and User Misery to get a full understanding of how your software is performing. ## Triage Performance Issues diff --git a/docs/product/tracing/index.mdx b/docs/product/tracing/index.mdx index 3074aeaeeede2..7c26744345724 100644 --- a/docs/product/tracing/index.mdx +++ b/docs/product/tracing/index.mdx @@ -47,7 +47,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 [Performance](https://sentry.io/orgredirect/organizations/:orgslug/performance/) 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 [Performance Monitoring](/product/performance/). +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/). ![An overview of the Performance page in Sentry.](./img/Performance-page.png) diff --git a/includes/performance-moving.mdx b/includes/performance-moving.mdx deleted file mode 100644 index 6cf8e4b05cf72..0000000000000 --- a/includes/performance-moving.mdx +++ /dev/null @@ -1,5 +0,0 @@ - - -To make it easier to see what's relevant for you, Sentry's Performance landing page is now being split into separate Frontend, Backend, and Mobile performance pages. They can all be found in the **Insights** tab. - - diff --git a/platform-includes/getting-started-primer/dotnet.mdx b/platform-includes/getting-started-primer/dotnet.mdx index 61c0c461b021b..d9daa39d904bf 100644 --- a/platform-includes/getting-started-primer/dotnet.mdx +++ b/platform-includes/getting-started-primer/dotnet.mdx @@ -14,7 +14,7 @@ This SDK is compatible with th 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](/product/performance/) creates transactions to track the performance of your application +- [Tracing](/product/insights/overview/) creates transactions to track the performance of your application - Automatically captures errors including: unhandled exceptions and unobserved task exceptions - Events enriched with device data - Offline caching of events when a device is unable to connect diff --git a/src/middleware.ts b/src/middleware.ts index ada6e174c8f9b..d1fa9346922e1 100644 --- a/src/middleware.ts +++ b/src/middleware.ts @@ -156,7 +156,7 @@ const USER_DOCS_REDIRECTS: Redirect[] = [ }, { from: '/product/data-management-settings/dynamic-sampling/', - to: '/product/performance/', + to: '/product/insights/overview/', }, { from: '/product/data-management-settings/event-grouping/', @@ -2433,93 +2433,125 @@ const USER_DOCS_REDIRECTS: Redirect[] = [ from: '/meta/relay/modes/', to: '/product/relay/modes/', }, + { + from: '/product/performance/', + to: '/product/sentry-basics/performance-monitoring/', + }, + { + from: '/product/performance/getting-started/', + to: '/product/insights/getting-started/', + }, + { + from: '/product/performance/filters-display/', + to: '/product/insights/overview/filters-display/', + }, + { + from: '/product/performance/filters-display/widgets/', + to: '/product/insights/overview/filters-display/widgets/', + }, + { + from: '/product/performance/trends/', + to: '/product/insights/overview/trends/', + }, + { + from: '/product/performance/transaction-summary/', + to: '/product/insights/overview/transaction-summary/', + }, + { + from: '/product/performance/metrics/', + to: '/product/insights/overview/metrics/', + }, + { + from: '/product/performance/performance-overhead/', + to: '/product/insights/performance-overhead/', + }, { from: '/product/performance/database/', - to: '/product/performance/queries/', + to: '/product/insights/backend/queries/', }, { from: '/product/performance/query-insights/', - to: '/product/performance/queries/', + to: '/product/insights/backend/queries/', }, { from: '/product/sentry-basics/metrics/', - to: '/product/performance/retention-priorities/', + to: '/product/insights/retention-priorities/', }, { from: '/product/sentry-basics/sampling/', - to: '/product/performance/retention-priorities/', + to: '/product/insights/retention-priorities/', }, { from: '/product/data-management-settings/server-side-sampling/', - to: '/product/performance/retention-priorities/', + to: '/product/insights/retention-priorities/', }, { from: '/product/data-management-settings/server-side-sampling/getting-started/', - to: '/product/performance/retention-priorities/', + to: '/product/insights/retention-priorities/', }, { from: '/product/data-management-settings/server-side-sampling/current-limitations/', - to: '/product/performance/retention-priorities/', + to: '/product/insights/retention-priorities/', }, { from: '/product/data-management-settings/server-side-sampling/sampling-configurations/', - to: '/product/performance/retention-priorities/', + to: '/product/insights/retention-priorities/', }, { from: '/product/data-management-settings/dynamic-sampling/current-limitations/', - to: '/product/performance/retention-priorities/', + to: '/product/insights/retention-priorities/', }, { from: '/product/data-management-settings/dynamic-sampling/sampling-configurations/', - to: '/product/performance/retention-priorities/', + to: '/product/insights/retention-priorities/', }, { from: '/product/performance/performance-at-scale/', - to: '/product/performance/retention-priorities/', + to: '/product/insights/retention-priorities/', }, { from: '/product/performance/performance-at-scale/getting-started/', - to: '/product/performance/retention-priorities/', + to: '/product/insights/retention-priorities/', }, { from: '/product/performance/performance-at-scale/benefits-performance-at-scale/', - to: '/product/performance/retention-priorities/', + to: '/product/insights/retention-priorities/', }, { from: '/performance/', - to: '/product/performance/', + to: '/product/insights/', }, { from: '/performance/display/', - to: '/product/performance/', + to: '/product/insights/', }, { from: '/performance-monitoring/performance/', - to: '/product/performance/', + to: '/product/insights/', }, { from: '/performance/performance-tab/', - to: '/product/performance/', + to: '/product/insights/overview', }, { from: '/performance/performance-homepage/', - to: '/product/performance/', + to: '/product/insights/', }, { from: '/performance-monitoring/setup/', - to: '/product/performance/getting-started/', + to: '/product/insights/getting-started/', }, { from: '/performance-monitoring/getting-started/', - to: '/product/performance/getting-started/', + to: '/product/insights/getting-started/', }, { from: '/performance-monitoring/performance/metrics/', - to: '/product/performance/metrics/', + to: '/product/insights/overview/metrics/', }, { from: '/product/performance/display/', - to: '/product/performance/filters-display/', + to: '/product/insights/overview/filters-display/', }, { from: '/product/issues/issue-owners/',