From ec50396706033ce486c717c5d85b4d35c9f0009c Mon Sep 17 00:00:00 2001 From: Christinarlong Date: Mon, 10 Nov 2025 15:48:18 -0800 Subject: [PATCH 1/2] update issue webhook docs --- .../integration-platform/webhooks/issues.mdx | 96 ++++++++++++------- 1 file changed, 59 insertions(+), 37 deletions(-) diff --git a/docs/organization/integrations/integration-platform/webhooks/issues.mdx b/docs/organization/integrations/integration-platform/webhooks/issues.mdx index 5201321a3c237..59faee0a3b26d 100644 --- a/docs/organization/integrations/integration-platform/webhooks/issues.mdx +++ b/docs/organization/integrations/integration-platform/webhooks/issues.mdx @@ -58,56 +58,78 @@ A status can mean multiple things, so substatus gives more details about the sta * `ignoreUserWindow`: Used with `ignoreUserCount` indicating the number of minutes that `ignoreUserCount` affected users will be ignored * `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/). +### issueCategory & issueType +`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). + +`issueType` allows for even more specifity on top of `issueCategory`, examples include `uptime_domain_failure` for `uptime` issues and `monitor_check_in_failure` for `cron` issues. + +The issue categories we currently support `issue.created` webhooks for are `OUTAGE`, `ERROR`, and FEEDBACK. + ```json { "action": "created", - "actor": { - "id": "sentry", - "name": "Sentry", - "type": "application" + "installation": { + "uuid": "24b397fc-a86e-43ef-9297-949e21b82480" }, "data": { "issue": { - "annotations": [], - "assignedTo": null, - "count": "1", - "culprit": "?(runner)", - "firstSeen": "2019-08-19T20:58:37.391000Z", - "hasSeen": false, - "id": "1170820242", - "isBookmarked": false, + "url": "https://sentry.io/api/0/organizations/example-org/issues/1234567890/", + "web_url": "https://example-org.sentry.io/issues/1234567890/", + "project_url": "https://example-org.sentry.io/issues/?project=4509877862268928", + "id": "1234567890", + "shareId": null, + "shortId": "PYTHON-Y", + "title": "Error generated with event_id: 495d375a-1df6-45c0-9890-34dae8e1b6a4(Priority: HIGH)", + "culprit": "test-transaction-0-41e49cd3-7252-441f-8d27-63a9ad697b0a", + "permalink": "https://example-org.sentry.io/issues/1234567890/", + "logger": "edge-function", + "level": "fatal", + "status": "unresolved", + "statusDetails": {}, + "substatus": "new", "isPublic": false, - "isSubscribed": false, - "lastSeen": "2019-08-19T20:58:37.391000Z", - "level": "error", - "logger": null, - "metadata": { - "filename": "/runner", - "type": "ReferenceError", - "value": "blooopy is not defined" - }, - "numComments": 0, - "permalink": null, "platform": "javascript", "project": { - "id": "1", - "name": "front-end", - "platform": "", - "slug": "front-end" + "id": "112313123123134", + "name": "python", + "slug": "python", + "platform": "python" }, - "shareId": null, - "shortId": "FRONT-END-9", - "status": "unresolved", - "statusDetails": {}, + "type": "default", + "metadata": { + "title": "Error generated with event_id: 495d375a-1df6-45c0-9890-34dae8e1b6a4(Priority: HIGH)", + "sdk": { + "name": "edge-function", + "name_normalized": "other" + }, + "severity": 1, + "severity_reason": "log_level_fatal", + "initial_priority": 75 + }, + "numComments": 0, + "assignedTo": null, + "isBookmarked": false, + "isSubscribed": false, "subscriptionDetails": null, - "substatus": "escalating", - "title": "ReferenceError: blooopy is not defined", - "type": "error", - "userCount": 1 + "hasSeen": false, + "annotations": [], + "issueType": "error", + "issueCategory": "error", + "priority": "high", + "priorityLockedAt": null, + "seerFixabilityScore": null, + "seerAutofixLastTriggered": null, + "isUnhandled": false, + "count": "3", + "userCount": 3, + "firstSeen": "2025-11-10T20:56:00.679000+00:00", + "lastSeen": "2025-11-10T20:56:00.738000+00:00" } }, - "installation": { - "uuid": "a8e5d37a-696c-4c54-adb5-b3f28d64c7de" + "actor": { + "type": "application", + "id": "example-app", + "name": "Example App" } } ``` From d0b872e5620ebfa3517562b81b93a516aba8c25e Mon Sep 17 00:00:00 2001 From: Christinarlong Date: Mon, 10 Nov 2025 15:51:28 -0800 Subject: [PATCH 2/2] typo --- .../integrations/integration-platform/webhooks/issues.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/organization/integrations/integration-platform/webhooks/issues.mdx b/docs/organization/integrations/integration-platform/webhooks/issues.mdx index 59faee0a3b26d..96599561e4a90 100644 --- a/docs/organization/integrations/integration-platform/webhooks/issues.mdx +++ b/docs/organization/integrations/integration-platform/webhooks/issues.mdx @@ -61,7 +61,7 @@ A status can mean multiple things, so substatus gives more details about the sta ### issueCategory & issueType `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). -`issueType` allows for even more specifity on top of `issueCategory`, examples include `uptime_domain_failure` for `uptime` issues and `monitor_check_in_failure` for `cron` issues. +`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. The issue categories we currently support `issue.created` webhooks for are `OUTAGE`, `ERROR`, and FEEDBACK.