feat(perf-detector-threshold-configuration) Updated detection criteri…

…a of performance issues. (#7420) * feat(perf-detector-threshold-configuration) Updated detection criteria of performance issues to include new detector threshold settings UI. * feat(perf-detector-threshold-configuration) Updated capitalization. Co-authored-by: vivianyentran <[email protected]> * feat(perf-detector-threshold-configuration) Updated capitalization. Co-authored-by: vivianyentran <[email protected]> * feat(perf-detector-threshold-configuration) Updated capitalization. Co-authored-by: vivianyentran <[email protected]> * feat(perf-detector-threshold-configuration) Updated capitalization. Co-authored-by: vivianyentran <[email protected]> * feat(perf-detector-threshold-configuration) Updated capitalization. Co-authored-by: vivianyentran <[email protected]> * feat(perf-detector-threshold-configuration) Updated capitalization. Co-authored-by: vivianyentran <[email protected]> * feat(perf-detector-threshold-configuration) Updated capitalization. Co-authored-by: vivianyentran <[email protected]> * feat(perf-detector-threshold-configuration) Updated capitalization. Co-authored-by: vivianyentran <[email protected]> * feat(perf-detector-threshold-configuration) Updated capitalization. Co-authored-by: vivianyentran <[email protected]> * feat(perf-detector-threshold-configuration) Updated capitalization. Co-authored-by: vivianyentran <[email protected]> * feat(perf-detector-threshold-configuration) Updated capitalization. Co-authored-by: vivianyentran <[email protected]> * feat(perf-detector-threshold-configuration) Updated capitalization. Co-authored-by: vivianyentran <[email protected]> * feat(perf-detector-threshold-configuration) Updated capitalization. Co-authored-by: vivianyentran <[email protected]> * feat(perf-detector-threshold-configuration) Updated capitalization. Co-authored-by: vivianyentran <[email protected]> * feat(perf-detector-threshold-configuration) Updated capitalization. Co-authored-by: vivianyentran <[email protected]> * feat(perf-detector-threshold-configuration) Updated capitalization. Co-authored-by: vivianyentran <[email protected]> --------- Co-authored-by: Abdullah Khan <[email protected]> Co-authored-by: vivianyentran <[email protected]>
getsentry · Jul 13, 2023 · a912878 · a912878 · vercel · Jul 13, 2023
1 parent 03e737b
commit a912878
Show file tree

Hide file tree

Showing 16 changed files with 40 additions and 8 deletions.
diff --git a/.../performance-issues/consecutive-db-queries/consecutive-db-detector-settings.png b/.../performance-issues/consecutive-db-queries/consecutive-db-detector-settings.png
diff --git a/...roduct/issues/issue-details/performance-issues/consecutive-db-queries/index.mdx b/...roduct/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
@@ -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/...issues/issue-details/performance-issues/db-on-main-thread-detector-settings.png b/...issues/issue-details/performance-issues/db-on-main-thread-detector-settings.png
diff --git a/...sues/issue-details/performance-issues/file-main-thread-io-detector-settings.png b/...sues/issue-details/performance-issues/file-main-thread-io-detector-settings.png
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
@@ -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/...cs/product/issues/issue-details/performance-issues/large-http-payload/index.mdx b/...cs/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/.../performance-issues/large-http-payload/large-http-payload-detector-settings.png b/.../performance-issues/large-http-payload/large-http-payload-detector-settings.png
diff --git a/...t/issues/issue-details/performance-issues/large-render-blocking-asset/index.mdx b/...t/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/...-issues/large-render-blocking-asset/render-blocking-asset-detector-settings.png b/...-issues/large-render-blocking-asset/render-blocking-asset-detector-settings.png
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
@@ -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/...ssues/issue-details/performance-issues/n-plus-one-queries-detector-settings.png b/...ssues/issue-details/performance-issues/n-plus-one-queries-detector-settings.png
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
@@ -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/...etails/performance-issues/slow-db-queries/slow-db-queries-detector-settings.png b/...etails/performance-issues/slow-db-queries/slow-db-queries-detector-settings.png
diff --git a/...cs/product/issues/issue-details/performance-issues/uncompressed-asset/index.mdx b/...cs/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/.../performance-issues/uncompressed-asset/uncompressed-asset-detector-settings.png b/.../performance-issues/uncompressed-asset/uncompressed-asset-detector-settings.png