Skip to content

Commit 9335ce9

Browse files
authored
chore(incidentio): Update docs with alert stuff (#13882)
## DESCRIBE YOUR PR Update docs for incident.io. Not sure we should be maintaining all of these but if they currently exist, it's worth mentioning all the features.. <img width="664" alt="image" src="https://github.com/user-attachments/assets/7f922b19-1f52-4a8a-9a13-fbb2aa37515a" /> ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. - [ ] Urgent deadline (GA date, etc.): <!-- ENTER DATE HERE --> - [ ] Other deadline: <!-- ENTER DATE HERE --> - [x] None: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it. Thanks in advance for your help! ## PRE-MERGE CHECKLIST *Make sure you've checked the following before merging your changes:* - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs)
1 parent 90328f1 commit 9335ce9

File tree

3 files changed

+15
-2
lines changed

3 files changed

+15
-2
lines changed
Loading
Loading

docs/organization/integrations/issue-tracking/incidentio/index.mdx

Lines changed: 15 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,6 @@ This integration is maintained and supported by the company that created it. For
1313
<Alert>
1414

1515
Sentry owner, manager, or admin permissions are required to install this integration.
16-
1716
incident.io **won't** work with self-hosted Sentry.
1817

1918
</Alert>
@@ -40,7 +39,7 @@ The Sentry issue is now attached to the incident:
4039

4140
![Incident with Sentry issue attached](./img/incidentio-attach-post.png)
4241

43-
### In sentry.io
42+
### In Sentry
4443

4544
To attach a Sentry issue to an incident in [sentry.io](https://sentry.io), navigate to a specific Sentry issue and find the "Linked Issues" section on the right panel. Click "Link incident.io issue" and select your active incident from the dropdown:
4645

@@ -51,3 +50,17 @@ To attach a Sentry issue to an incident in [sentry.io](https://sentry.io), navig
5150
The incident's Slack channel will be updated with attached Sentry issue comments, edited comments, and when the Sentry issue is resolved:
5251

5352
![Synced comments from Sentry on an incident in Slack](./img/incidentio-issue-sync.png)
53+
54+
55+
## Alerting
56+
57+
Once installed, you can also set Sentry to be an alert source for incidents.
58+
59+
![incident.io alert setup](./img/incidentio-alert-setup.png)
60+
61+
Afterward, within Sentry you can connect it to that newly created source in an alert rule.
62+
63+
![incident.io alert rule](./img/incidentio-alert-rule.png)
64+
65+
66+
When the alert fires, it'll create an incident on incident.io, with all the downstream affects you set up on that side.

0 commit comments

Comments
 (0)