Sentry

Start an investigation when a Sentry alert fires, configured with sentry.yaml.

Sentry can start a session when an issue alert fires or a metric alert becomes critical. The Sentry integration is not generally released yet; contact Support for access.

Connect and configure alerts

  1. Connect Sentry from the Ellipsis integrations settings and complete the installation in your Sentry organization.
  2. In Sentry, set each project's issue or metric alert rule to notify the Ellipsis integration. Installing the integration alone sends no alerts.
  3. Merge sentry.yaml at the root of your organization's .ellipsis repository.
  4. Send a test alert from Sentry and check that a session starts and delivers its report.

Sentry credentials stay in the integration settings; sentry.yaml only chooses which alerts start a session and what the session does. Slack reports also need a connected Slack workspace.

Route alerts

This handler investigates alerts from every project in one Sentry organization and posts a short Slack report for each:

1
ellipsis:
2
kind: sentry
3
name: Production error reports
4
5
sentry:
6
organizations: [my-sentry-org]
7
projects: ['*']
8
on: [issue_alert, metric_alert]
9
10
session:
11
codex:
12
prompt: |
13
Investigate the alert and send one report to #eng-ops, at most
14
three short lines and 70 words. Include the project, Sentry link,
15
impact, and next step. Link the causing PR only when supported by
16
evidence. Tag its author only after verifying their Slack identity.
17
If attribution is uncertain, say so. Do not open a fix PR.
18
model: gpt-6-sol
19
environment:
20
repositories:
21
- name: api-repo
22
mcp_servers:
23
- name: slack
24
permissions:
25
github:
26
permissions: read_only
27
budget:
28
session: 2

An alert starts a session only when its organization, project, and alert type all match. Don't mix '*' with names in the same list.

Delivery

An issue alert starts at most one investigation every 6 hours. A metric alert starts one only when it becomes critical, not on warning or resolved. Repeated deliveries of the same alert are ignored.

While sentry.yaml exists, it handles every Sentry alert, and agents with a sentry trigger don't run, even when the file is disabled. Delete the file to use those agents instead.

The default-branch version is live, and an invalid edit keeps the last valid one. Only the copy in the .ellipsis repository counts.

Fields

Identifies the file.

Which alerts start a session. An alert matches when its organization, project, and alert type all match; don't mix '*' with names in the same list.

Works like an agent's session block, including budget.

On this page

Connect and configure alertsRoute alertsDeliveryFields
Schedule a demo