Open GitHub Issues for Incidents

Connect with GitHub

1. On the GitHub card, click "Connect with GitHub".
2. GitHub asks you to install the SutramX app. Choose the repositories that should receive incident issues and click Install.
3. Back in SutramX, pick the repository if you chose more than one. That is it: no tokens to create or renew.

The app can only read and write issues in the repositories you chose. You can change or remove its access at any time in GitHub under Settings → Applications.

Or use a personal access token

1. In GitHub, go to Settings → Developer settings → Personal access tokens → Fine-grained tokens → Generate new token.
2. Under Repository access, choose "Only select repositories" and pick the repository that should receive incident issues.
3. Under Permissions → Repository permissions, set Issues to "Read and write". Nothing else is needed.
4. Set an expiry that suits your policy, generate the token and copy it.

Then choose "Use a personal access token instead" on the GitHub card, enter the repository as owner/repo and paste the token. The connection test checks that the token can reach the repository. It does not create an issue.

What happens during an incident

• Monitor goes down: an issue is opened with the monitor, the failure reason and a link to the incident.
• Monitor recovers: the same issue is closed.

Connect it in SutramX

1. Sign in to the SutramX dashboard and open Integrations & API in the sidebar, then the Integrations tab.
2. On the GitHub issues card, click Connect. Where you see "Connect with …", you just sign in and approve. Otherwise the card shows two or three short steps and one box to paste into.
3. Already have a webhook link? Paste it into the box at the top of the page and SutramX works out which service it belongs to.
4. SutramX sends a test straight away so you can confirm delivery before any real incident.
5. Optional: use Routing to send only some monitors or groups to this channel.

You can connect more than one GitHub issues destination. Each connection has its own routing, so different channels can receive different monitors.

Other incident and developer integrations

• Opsgenie alerts setup: Create and auto-close alerts with an API integration key.
• Email & team members alerts setup: Invite teammates, then choose exactly who receives alert emails.