Sentry

The Sentry integration lets alerts start agents: an issue or metric alert fires and an agent wakes up with the alert's context, reads the stack trace, and posts a diagnosis or opens a fix.

Connect

1. Open Integrations → Sentry in the dashboard and click Connect Sentry. This sends you to Sentry to install the Ellipsis app in your Sentry organization.
2. Approve the installation in Sentry. Sentry redirects you back to Ellipsis, where you pick which Ellipsis account to connect it to and click Connect Sentry to finish.
3. In Sentry, add Send a notification via Ellipsis as the action on any alert rule you want to reach agents. Alerts only flow through rules that name Ellipsis.

An account can connect several Sentry organizations; each is listed on the same dashboard page with its own Disconnect. Disconnecting (or uninstalling the app from Sentry itself) stops alerts from starting agents and removes agent access to that organization's issues.

What it enables

• Alert-triggered diagnosis agents. A sentry react trigger starts a session when an alert fires: issue_alert, metric_alert (on entering critical), or both, filtered by Sentry project. The trigger block: Triggers. The full worked agent, with the diagnosis it posts: Turn Sentry alerts into root-cause diagnoses.
• Storms stay one investigation. A recurring Sentry issue reaches agents at most once every 6 hours. Within the window, re-fires are dropped; across windows, a re-fire tells the existing investigation "this alert fired again" instead of spawning a duplicate. An alert rule configured to fire per event never produces a session per event.
• The alert as context. The triggering session receives the issue, the alert rule, and the stack trace, and can pull the full event from Sentry's API when it needs more.