Sentry connector
The Sentry connector connects directly to the Sentry API. It lets a workflow or agent triage Sentry issues — list, read, resolve, ignore, reopen, and assign — plus bulk-update issues, provision issue alert rules, and audit monitor coverage, without opening the Sentry console.
This is a custom connector that uses Sentry's REST API with Bearer token authentication. You configure your Sentry organization slug and an auth token when creating the connector.
You can create a Sentry connector in Stack Management > Connectors.
- Organization slug
- The slug of your Sentry organization, found in the URL:
sentry.io/organizations/<slug>/. - API base URL
- Optional. Leave empty to use Sentry SaaS (
https://sentry.io/api/0). If your organization uses a region-specific data storage location, use its regional domain instead, for examplehttps://us.sentry.io/api/0orhttps://de.sentry.io/api/0. Set this for a self-hosted Sentry instance, for examplehttps://sentry.example.com/api/0. - Authentication
- Bearer token. Use a Sentry auth token with
org:read,project:read,event:read, andevent:writescopes (addevent:admintoo if you plan to usedeleteIssue).
| Action | Description |
|---|---|
listIssues |
List issues, optionally scoped to a project, filtered by search query, environment, or time window. Parameters: project, query, statsPeriod, environment, sort, cursor, limit. |
getIssue |
Get the full record for a single issue. Parameters: issueId (required). |
resolveIssue |
Resolve an issue. Parameters: issueId (required), inNextRelease. |
ignoreIssue |
Ignore (archive) an issue. Parameters: issueId (required), ignoreDuration. |
unresolveIssue |
Move an issue back to unresolved. Parameters: issueId (required). |
assignIssue |
Assign an issue to a user or team. Parameters: issueId (required), assignedTo (required). |
listIssueEvents |
List the events recorded under an issue. Parameters: issueId (required), cursor, full. |
getEvent |
Get one event's full detail (stack trace, tags, context). Parameters: project (required), eventId (required). |
bulkUpdateIssues |
Update status and/or assignee for multiple issues in one call. Parameters: project (required), issueIds (required), status, assignedTo (at least one of status/assignedTo is required). |
deleteIssue |
Permanently delete an issue. Requires the event:admin scope. Parameters: issueId (required). |
listProjects |
List the organization's projects. Parameters: cursor. |
listIssueAlertRules |
List issue alert rules configured on a project. Parameters: project (required), cursor. |
createIssueAlertRule |
Create a new issue alert rule. Parameters: project (required), name (required), conditions (required), actions (required), actionMatch, frequency. |
updateIssueAlertRule |
Update an existing issue alert rule. Parameters: project (required), ruleId (required), name, actionMatch, conditions, actions, frequency. |
Use the Action configuration settings to customize connector networking, such as proxies, certificates, or TLS settings. You can set configurations that apply to all your connectors or use xpack.actions.customHostSettings to set per-host configurations.
- Log in to your Sentry account.
- Go to Settings > Developer Settings > New Internal Integration (or, for a personal auth token, User Settings > User Auth Tokens).
- Grant the scopes
org:read,project:read,event:read, andevent:write(addalerts:writeif you plan to provision issue alert rules, andevent:adminif you plan to usedeleteIssue). - Save the integration and copy the generated token.
- When configuring the connector, enter the token as the Bearer token, and enter your organization slug (from your Sentry URL) in the Organization slug field.