You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/organization/integrations/integration-platform/webhooks/issues.mdx
+59-37Lines changed: 59 additions & 37 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,56 +58,78 @@ A status can mean multiple things, so substatus gives more details about the sta
58
58
*`ignoreUserWindow`: Used with `ignoreUserCount` indicating the number of minutes that `ignoreUserCount` affected users will be ignored
59
59
*`ignoreDuration`: The duration (in minutes) that an archived issue should be ignored before it gets escalated. Increase in the number of users affected or the number of occurrences will not escalate before this duration has passed unless there is a spike. To learn more about how this works, see [Escalating Issues Algorithm](/product/issues/states-triage/escalating-issues/).
60
60
61
+
### issueCategory & issueType
62
+
`issueCategory` and `issueType` provide more detail to distinguish different issues from eachother. For `issueCategory` variations include, `outage` (for issues created from `uptime` and `cron` monitors) and `error` (for issues created from an error event).
63
+
64
+
`issueType` allows for even more specificity on top of `issueCategory`, examples include `uptime_domain_failure` for `uptime` issues and `monitor_check_in_failure` for `cron` issues.
65
+
66
+
The issue categories we currently support `issue.created` webhooks for are `OUTAGE`, `ERROR`, and FEEDBACK.
0 commit comments