Skip to content

update (Seer): Updating root cause analysis config options #16280

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
sfanahata wants to merge 1 commit into
base: master
Choose a base branch
from
+4 −6
Open

update (Seer): Updating root cause analysis config options #16280

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file removed docs/product/ai-in-sentry/seer/img/repo-settings.png
View file
Open in desktop
Binary file not shown.
10 changes: 4 additions & 6 deletions docs/product/ai-in-sentry/seer/root-cause-analysis/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,10 +1,10 @@
---
title: Root Cause Analysis
description: >-
Use Seer's Root Cause Analysis to automatically find the root cause of issues and
generate code fixes.
Use Seer's Root Cause Analysis to automatically find the root cause of issues
and generate code fixes.
sidebar_order: 20
og_image: /og-images/product-ai-in-sentry-seer-issue-fix.png
og_image: /og-images/product-ai-in-sentry-seer-root-cause-analysis.png
---

**Root Cause Analysis** is Seer's collaborative workflow to find the root cause of, and solution to, issues. It uses Sentry's context (issue details, tracing data, logs, and profiles), your codebases (integrated through GitHub), and its interactions with you to identify and reason through problems in your code.
Expand Down Expand Up @@ -67,14 +67,12 @@ Root Cause Analysis's default behavior can be customized in several ways:

1. You can manually customize the repositories it has access to
2. You can define the default branch it should use in each repository
3. You can add any additional custom context that that may be useful within the scope of each individual repository
3. You can set an override for the default branch in each repository

<Alert>
Seer already automatically parses rules files from [Cursor](https://docs.cursor.com/context/rules), [Windsurf](https://windsurf.com/editor/directory), [Cline](https://docs.cline.bot/features/cline-rules), and [Claude Code](https://docs.anthropic.com/en/docs/claude-code/tutorials#create-an-effective-claude-md-file)
</Alert>

![Screenshot of the repository settings page](../img/repo-settings.png)

## Best Practices

- The more Sentry context you have, the better equipped Seer will be to help: consider instrumenting your application to collect traces, profiles and logs, and send them to Sentry.
Expand Down