diff --git a/docs/product/issues/issue-details/performance-issues/img/performance-issue-configuration.png b/docs/product/issues/issue-details/performance-issues/img/performance-issue-configuration.png new file mode 100644 index 0000000000000..a2ecec14bdac9 Binary files /dev/null and b/docs/product/issues/issue-details/performance-issues/img/performance-issue-configuration.png differ diff --git a/docs/product/issues/issue-details/performance-issues/index.mdx b/docs/product/issues/issue-details/performance-issues/index.mdx index 2c40ec94e1eeb..8122e1cd9e014 100644 --- a/docs/product/issues/issue-details/performance-issues/index.mdx +++ b/docs/product/issues/issue-details/performance-issues/index.mdx @@ -30,7 +30,13 @@ Span evidence is information that explains the performance problem in the contex The "Event Grouping Information" section provides details of how Sentry fingerprinted the event into the group. You can see which parts of the span evidence contributed to the fingerprint. -## Performance Issue Types +## Configuration + +As a Project Admin, you can also manage individual settings for each performance issue detector in **Project Settings > Performance**. Here, you can raise or lower the thresholds for what Sentry considers a performance issue for each project, or disable detection altogether. + +![Performance issue configuration](./img/performance-issue-configuration.png) + +## Issue Types The following is a list of available performance issues: @@ -136,11 +142,9 @@ The following is a list of available performance issues: -## Performance Issue Limitations +## Limitations Performance issues currently have the following limitations: -- Performance issues can't be merged or deleted +- Performance issues cannot be merged - Custom fingerprinting and grouping can't be applied to performance issues - -We're working on removing some or all of these limitations.