Skip to content
Open
Changes from all commits
Commits
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
13 changes: 13 additions & 0 deletions docs/integrations/integration-platform/webhooks/seer.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,19 @@ description: "Learn more about Sentry's integration platform Seer webhooks for I

Sentry integrations that have subscribed to Seer webhooks can receive notifications about the Seer [Autofix](/product/ai-in-sentry/seer/autofix/) process. These webhooks allow you to track the progress of root cause analysis, solution generation, and code fixes.

<Alert level="warning" title="Upcoming changes to Seer webhooks">

Over the coming weeks, we'll move organizations to a new Autofix flow where one run finds the root cause and, if your settings allow it, writes the fix and opens a PR. Once your organization moves:

- `seer.solution_started`, `seer.solution_completed` and `seer.coding_started` are no longer sent.
- `seer.root_cause_completed` adds a `headline` field. `one_line_description` now holds the cause, `five_whys` and `reproduction_steps` are empty, and `relevant_repo` is omitted.
- A run that stops before finding a root cause doesn't send `seer.root_cause_completed`.
- A run that opens a PR sends both `seer.coding_completed` and `seer.pr_created`.

We'll remove `five_whys` and `reproduction_steps` later, with at least 30 days' notice in the [changelog](https://sentry.io/changelog/seer-autofix-single-run/).

</Alert>

## Sentry-Hook-Resource Header

`'Sentry-Hook-Resource': 'seer'`
Expand Down
Loading