diff --git a/docs/product/ai-in-sentry/seer/root-cause-analysis/index.mdx b/docs/product/ai-in-sentry/seer/root-cause-analysis/index.mdx index 2e98254dd3e244..938b0e448dd791 100644 --- a/docs/product/ai-in-sentry/seer/root-cause-analysis/index.mdx +++ b/docs/product/ai-in-sentry/seer/root-cause-analysis/index.mdx @@ -64,6 +64,20 @@ You can disable code generation for your organization [here](https://sentry.io/o ![Screenshot of Seer showing code it generated =800x](../img/coding-step.png) +## Root Cause Analysis in Slack [Beta] + + +This feature is currently in beta. Beta features are still a work in progress and may have bugs. We recognize the irony. + + +If you have the [Slack integration](/organization/integrations/notification-incidents/slack/) enabled, you can trigger Root Cause Analysis from a Slack message. + +1. Invite Sentry to your Slack channel (@Sentry) +2. Make sure you have [Issue Alerts](/organization/integrations/notification-incidents/slack/#issue-alerts) configured to send alerts to the Slack channel +3. When a new issue is shown on the channel, it will include an option to *Fix with Seer* + +Clicking *Fix with Seer* will trigger Root Cause Analysis for the issue. You can wait to see the result posted in the issue thread, or go to Sentry to see the process. Seer will prompt you to take next steps once it has finished running, including planning a solution, generating code, and pushing it to your codebase. + ## What Root Cause Analysis Uses Seer handles access to a wide variety of data sources and tools. While debugging issues, it may examine: