diff --git a/docs/product/issues/issue-details/performance-issues/consecutive-db-queries/img/consecutive-db-detector-settings.png b/docs/product/issues/issue-details/performance-issues/consecutive-db-queries/img/consecutive-db-detector-settings.png index 54648ba99bd53b..14362a7371b732 100644 Binary files a/docs/product/issues/issue-details/performance-issues/consecutive-db-queries/img/consecutive-db-detector-settings.png and b/docs/product/issues/issue-details/performance-issues/consecutive-db-queries/img/consecutive-db-detector-settings.png differ diff --git a/docs/product/issues/issue-details/performance-issues/consecutive-db-queries/index.mdx b/docs/product/issues/issue-details/performance-issues/consecutive-db-queries/index.mdx index 3454ba505e70e0..1d270b5334e0d6 100644 --- a/docs/product/issues/issue-details/performance-issues/consecutive-db-queries/index.mdx +++ b/docs/product/issues/issue-details/performance-issues/consecutive-db-queries/index.mdx @@ -25,7 +25,7 @@ Once these spans are found, the following must also hold true: 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**: +You can configure detector thresholds for Consecutive DB Queries issues in **Project Settings > Performance**. ![Consecutive DB Queries detector threshold settings](./img/consecutive-db-detector-settings.png) diff --git a/docs/product/issues/issue-details/performance-issues/consecutive-http/img/consecutive-http-threshold-settings.png b/docs/product/issues/issue-details/performance-issues/consecutive-http/img/consecutive-http-threshold-settings.png index d8dd0682cb3cc4..a563e890340bc7 100644 Binary files a/docs/product/issues/issue-details/performance-issues/consecutive-http/img/consecutive-http-threshold-settings.png and b/docs/product/issues/issue-details/performance-issues/consecutive-http/img/consecutive-http-threshold-settings.png differ diff --git a/docs/product/issues/issue-details/performance-issues/consecutive-http/index.mdx b/docs/product/issues/issue-details/performance-issues/consecutive-http/index.mdx index e4e83b40d223e9..ab82eb6b63df9b 100644 --- a/docs/product/issues/issue-details/performance-issues/consecutive-http/index.mdx +++ b/docs/product/issues/issue-details/performance-issues/consecutive-http/index.mdx @@ -32,7 +32,7 @@ Once these spans are found, the following must also hold true: If Sentry doesn't detect a Consecutive HTTP 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 HTTP issues in **Project Settings > Performance**: +You can configure detector thresholds for Consecutive HTTP issues in **Project Settings > Performance**. ![Consecutive HTTP detector threshold settings](./img/consecutive-http-threshold-settings.png) diff --git a/docs/product/issues/issue-details/performance-issues/file-main-thread-io.mdx b/docs/product/issues/issue-details/performance-issues/file-main-thread-io.mdx index d1ca9db0f4f0a7..22b76aa40dde9f 100644 --- a/docs/product/issues/issue-details/performance-issues/file-main-thread-io.mdx +++ b/docs/product/issues/issue-details/performance-issues/file-main-thread-io.mdx @@ -14,7 +14,7 @@ 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 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**: +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](./img/file-main-thread-io-detector-settings.png) diff --git a/docs/product/issues/issue-details/performance-issues/img/file-main-thread-io-detector-settings.png b/docs/product/issues/issue-details/performance-issues/img/file-main-thread-io-detector-settings.png index b25bfff8569cee..c0aec1dfa26b6b 100644 Binary files a/docs/product/issues/issue-details/performance-issues/img/file-main-thread-io-detector-settings.png and b/docs/product/issues/issue-details/performance-issues/img/file-main-thread-io-detector-settings.png differ diff --git a/docs/product/issues/issue-details/performance-issues/slow-db-queries/img/slow-db-queries-detector-settings.png b/docs/product/issues/issue-details/performance-issues/slow-db-queries/img/slow-db-queries-detector-settings.png index a1d921ba91568f..eb423f1eb41d49 100644 Binary files a/docs/product/issues/issue-details/performance-issues/slow-db-queries/img/slow-db-queries-detector-settings.png and b/docs/product/issues/issue-details/performance-issues/slow-db-queries/img/slow-db-queries-detector-settings.png differ diff --git a/docs/product/issues/issue-details/performance-issues/slow-db-queries/index.mdx b/docs/product/issues/issue-details/performance-issues/slow-db-queries/index.mdx index 0197cad12b94ba..7afb9fd48b7cc2 100644 --- a/docs/product/issues/issue-details/performance-issues/slow-db-queries/index.mdx +++ b/docs/product/issues/issue-details/performance-issues/slow-db-queries/index.mdx @@ -18,7 +18,7 @@ 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 `500ms`. More specifically, the issue will be created only if the same query is detected as a slow query 100 times. The counter resets after 24 hours without detecting the slow query. -You can configure detector thresholds for Slow DB Query issues in **Project Settings > Performance**: +You can configure detector thresholds for Slow DB Query issues in **Project Settings > Performance**. ![Slow DB Query detector threshold settings](./img/slow-db-queries-detector-settings.png)