diff --git a/src/docs/product/issues/issue-details/performance-issues/consecutive-db-queries/consecutive-db-detector-settings.png b/src/docs/product/issues/issue-details/performance-issues/consecutive-db-queries/consecutive-db-detector-settings.png new file mode 100644 index 0000000000000..d438693928b50 Binary files /dev/null and b/src/docs/product/issues/issue-details/performance-issues/consecutive-db-queries/consecutive-db-detector-settings.png differ diff --git a/src/docs/product/issues/issue-details/performance-issues/consecutive-db-queries/index.mdx b/src/docs/product/issues/issue-details/performance-issues/consecutive-db-queries/index.mdx index 0919015b8f7af..3dfbc52e984c7 100644 --- a/src/docs/product/issues/issue-details/performance-issues/consecutive-db-queries/index.mdx +++ b/src/docs/product/issues/issue-details/performance-issues/consecutive-db-queries/index.mdx @@ -23,11 +23,15 @@ Once these spans are found, the following must also hold true: - Ratio between the maximum time saved and the duration of the sequential spans must exceed a 0.1 threshold - Total duration of each parallelizable span must exceed a 30ms threshold -If Sentry isn't detecting a Consecutive DB issue where you expect one, it's probably because the transaction didn't meet one of the above criteria. +If Sentry isn't detecting a consecutive DB issue where you expect one, it's probably because the transaction didn't meet one of the above criteria. + +You can configure detector thresholds for consecutive DB queries issues in **Project Settings > Performance**: + +![Consecutive DB Queries detector threshold settings](consecutive-db-detector-settings.png) ## Span Evidence -You can identify a Consecutive DB queries problem by four main aspects in the "Span Evidence" section: +You can identify a consecutive DB queries problem by four main aspects in the "Span Evidence" section: - Transaction name - Starting Span - The first span in a set of consecutive spans diff --git a/src/docs/product/issues/issue-details/performance-issues/db-main-thread-io.mdx b/src/docs/product/issues/issue-details/performance-issues/db-main-thread-io.mdx index 9e2a3677e5c3c..afdfceb55dc20 100644 --- a/src/docs/product/issues/issue-details/performance-issues/db-main-thread-io.mdx +++ b/src/docs/product/issues/issue-details/performance-issues/db-main-thread-io.mdx @@ -16,9 +16,13 @@ The main UI thread in a mobile application handles user interface events such as The detector for this performance issue looks at the total non-overlapping duration for database spans on the main thread. If it exceeds 16ms, a Performance Issue is created. +You can configure detector thresholds for database on main thread issues in **Project Settings > Performance**: + +![Database on Main Thread detector threshold settings](db-on-main-thread-detector-settings.png) + ## Span Evidence -Span evidence identifies the root cause of the Database on Main Thread problem by showing you three main aspects: +Span evidence identifies the root cause of the database on main thread problem by showing you three main aspects: - **Transaction name** - **Parent Span:** Where the database spans occurred diff --git a/src/docs/product/issues/issue-details/performance-issues/db-on-main-thread-detector-settings.png b/src/docs/product/issues/issue-details/performance-issues/db-on-main-thread-detector-settings.png new file mode 100644 index 0000000000000..1308efc90f7e6 Binary files /dev/null and b/src/docs/product/issues/issue-details/performance-issues/db-on-main-thread-detector-settings.png differ diff --git a/src/docs/product/issues/issue-details/performance-issues/file-main-thread-io-detector-settings.png b/src/docs/product/issues/issue-details/performance-issues/file-main-thread-io-detector-settings.png new file mode 100644 index 0000000000000..099ecf51b5771 Binary files /dev/null and b/src/docs/product/issues/issue-details/performance-issues/file-main-thread-io-detector-settings.png differ diff --git a/src/docs/product/issues/issue-details/performance-issues/file-main-thread-io.mdx b/src/docs/product/issues/issue-details/performance-issues/file-main-thread-io.mdx index 636adb9395303..2bf3cad99dc91 100644 --- a/src/docs/product/issues/issue-details/performance-issues/file-main-thread-io.mdx +++ b/src/docs/product/issues/issue-details/performance-issues/file-main-thread-io.mdx @@ -8,7 +8,11 @@ The main UI thread in a mobile application handles user interface events such as ## Detection Criteria -The detector for this performance issue looks at the total non-overlapping duration for File I/O spans. If it exceeds 16ms, a Performance Issue is created. +The detector for this performance issue looks at the total non-overlapping duration for file I/O spans. If it exceeds 16ms, a performance issue is created. + +You can configure detector thresholds for file I/O on main thread issues in **Project Settings > Performance**: + +![File I/O on Main Thread detector threshold settings](file-main-thread-io-detector-settings.png) ## Span Evidence diff --git a/src/docs/product/issues/issue-details/performance-issues/large-http-payload/index.mdx b/src/docs/product/issues/issue-details/performance-issues/large-http-payload/index.mdx index da187cf13c7e3..4a713567863cc 100644 --- a/src/docs/product/issues/issue-details/performance-issues/large-http-payload/index.mdx +++ b/src/docs/product/issues/issue-details/performance-issues/large-http-payload/index.mdx @@ -17,7 +17,11 @@ The detector for this performance issue looks for a single http span that meets - The HTTP span must have an `http.response_content_length` (added by the `@sentry/browser` SDK, version `7.53.0`) that exceeds 500kb - The HTTP span duration must exceed 100ms -If Sentry isn't detecting a Large HTTP Payload issue where you expect one, it's probably because the transaction didn't meet one of the above criteria. +If Sentry isn't detecting a large HTTP payload issue where you expect one, it's probably because the transaction didn't meet one of the above criteria. + +You can configure detector thresholds for large HTTP payload issues in **Project Settings > Performance**: + +![Large HTTP Payload detector threshold settings](large-http-payload-detector-settings.png) ## Span Evidence diff --git a/src/docs/product/issues/issue-details/performance-issues/large-http-payload/large-http-payload-detector-settings.png b/src/docs/product/issues/issue-details/performance-issues/large-http-payload/large-http-payload-detector-settings.png new file mode 100644 index 0000000000000..21b02683affd2 Binary files /dev/null and b/src/docs/product/issues/issue-details/performance-issues/large-http-payload/large-http-payload-detector-settings.png differ diff --git a/src/docs/product/issues/issue-details/performance-issues/large-render-blocking-asset/index.mdx b/src/docs/product/issues/issue-details/performance-issues/large-render-blocking-asset/index.mdx index ff08697613e0e..399532c4485d4 100644 --- a/src/docs/product/issues/issue-details/performance-issues/large-render-blocking-asset/index.mdx +++ b/src/docs/product/issues/issue-details/performance-issues/large-render-blocking-asset/index.mdx @@ -18,9 +18,13 @@ The detector for this performance issue looks for specific asset (resource) span - The [First Contentful Paint (FCP)](/product/performance/web-vitals/#first-contentful-paint-fcp) of the transaction must be at least `2` seconds (with an upper bound of `10` seconds to eliminate outliers). - The span's duration must be at least `33%` of the FCP. +You can configure detector thresholds for large render blocking asset issues in **Project Settings > Performance**: + +![Large Render Blocking Asset detector threshold settings](render-blocking-asset-detector-settings.png) + ## Span Evidence -You can get additional information about your Large Render Blocking Asset problem by looking at four aspects in the "Span Evidence" section: +You can get additional information about your large render blocking asset problem by looking at four aspects in the "Span Evidence" section: - Transaction name - Asset URL diff --git a/src/docs/product/issues/issue-details/performance-issues/large-render-blocking-asset/render-blocking-asset-detector-settings.png b/src/docs/product/issues/issue-details/performance-issues/large-render-blocking-asset/render-blocking-asset-detector-settings.png new file mode 100644 index 0000000000000..0b93d9de32d6a Binary files /dev/null and b/src/docs/product/issues/issue-details/performance-issues/large-render-blocking-asset/render-blocking-asset-detector-settings.png differ diff --git a/src/docs/product/issues/issue-details/performance-issues/n-one-queries.mdx b/src/docs/product/issues/issue-details/performance-issues/n-one-queries.mdx index 2dadf1d3dc93c..693159ff26377 100644 --- a/src/docs/product/issues/issue-details/performance-issues/n-one-queries.mdx +++ b/src/docs/product/issues/issue-details/performance-issues/n-one-queries.mdx @@ -19,6 +19,10 @@ The detector for performance issues looks for a set of sequential, non-overlappi If Sentry is not detecting an N+1 issue where you expect one, it's probably because the transaction didn't meet one of the above criteria. +You can configure detector thresholds for N+1 queries issues in **Project Settings > Performance**: + +![N+1 Query detector threshold settings](n-plus-one-queries-detector-settings.png) + ## Span Evidence The evidence for an N+1 queries problem has four main aspects: diff --git a/src/docs/product/issues/issue-details/performance-issues/n-plus-one-queries-detector-settings.png b/src/docs/product/issues/issue-details/performance-issues/n-plus-one-queries-detector-settings.png new file mode 100644 index 0000000000000..78e02ba2126d1 Binary files /dev/null and b/src/docs/product/issues/issue-details/performance-issues/n-plus-one-queries-detector-settings.png differ diff --git a/src/docs/product/issues/issue-details/performance-issues/slow-db-queries/index.mdx b/src/docs/product/issues/issue-details/performance-issues/slow-db-queries/index.mdx index d37ef6671d825..fc1e820506aad 100644 --- a/src/docs/product/issues/issue-details/performance-issues/slow-db-queries/index.mdx +++ b/src/docs/product/issues/issue-details/performance-issues/slow-db-queries/index.mdx @@ -19,9 +19,13 @@ The detector for this performance issue looks at singular database spans with th Keep in mind, an issue won't be created unless the query in question is _consistently_ taking longer than `1000ms`. More specifically, the issue will be created only if the same query is detected as a slow query in 100 events within a 24-hour period. +You can configure detector thresholds for slow DB queries issues in **Project Settings > Performance**: + +![Slow DB Query detector threshold settings](slow-db-queries-detector-settings.png) + ## Span Evidence -You can get additional information about your Slow DB Query by looking at the following fields in the "Span Evidence": +You can get additional information about your slow DB query by looking at the following fields in the "Span Evidence": - Transaction name - Slow DB Query diff --git a/src/docs/product/issues/issue-details/performance-issues/slow-db-queries/slow-db-queries-detector-settings.png b/src/docs/product/issues/issue-details/performance-issues/slow-db-queries/slow-db-queries-detector-settings.png new file mode 100644 index 0000000000000..789ab1a34a1dd Binary files /dev/null and b/src/docs/product/issues/issue-details/performance-issues/slow-db-queries/slow-db-queries-detector-settings.png differ diff --git a/src/docs/product/issues/issue-details/performance-issues/uncompressed-asset/index.mdx b/src/docs/product/issues/issue-details/performance-issues/uncompressed-asset/index.mdx index 936b4e39f61f5..f0300aaea7794 100644 --- a/src/docs/product/issues/issue-details/performance-issues/uncompressed-asset/index.mdx +++ b/src/docs/product/issues/issue-details/performance-issues/uncompressed-asset/index.mdx @@ -19,9 +19,13 @@ The detector for this performance issue looks for specific asset (resource) span If Sentry isn't detecting an uncompressed asset issue where you expect one, it's probably because the transaction didn't meet one of the above criteria. +You can configure detector thresholds for uncompressed asset issues in **Project Settings > Performance**: + +![Uncompressed Asset detector threshold settings](uncompressed-asset-detector-settings.png) + ## Span Evidence -You can identify an Uncompressed Asset problem by four main aspects in the "Span Evidence" section: +You can identify an uncompressed asset problem by four main aspects in the "Span Evidence" section: - Transaction name - Slow resource span - The uncompressed slow span, usually containing the asset url diff --git a/src/docs/product/issues/issue-details/performance-issues/uncompressed-asset/uncompressed-asset-detector-settings.png b/src/docs/product/issues/issue-details/performance-issues/uncompressed-asset/uncompressed-asset-detector-settings.png new file mode 100644 index 0000000000000..87d07baa5a347 Binary files /dev/null and b/src/docs/product/issues/issue-details/performance-issues/uncompressed-asset/uncompressed-asset-detector-settings.png differ