Sentry Error Triage
By i n e s · Published · Updated
Turns a pile of new production errors into a short list of distinct causes, marks which ones your code owns, and drafts a ticket for each.
Prompt template
## Sentry Error Triage Triage these new production errors. - Error list: [textarea: Paste titles and counts and first-seen times] - Stack traces: [textarea: Paste the top frames of the noisiest errors] - Recent releases: [textarea: Versions and dates and what shipped] - Our code lives in: [text: Folder names or package names] - Release under suspicion: [text: Version or none] - Ticket format: [dropdown: Plain text, Markdown, Jira style] Group errors by root cause, not by message: several titles often share one failing line or one bad input. For each group state the likely cause, the number of users or events affected, and when it first appeared relative to the releases. Decide ownership by the top in-app stack frame: Ours when it points into the listed code, External when it comes from a browser extension, a bot, a dependency or a third-party script, and Unclear when the trace is missing. Rank Ours groups by user impact and recency. Then write one ticket per Ours group with a title, evidence, a suspected fix, how to reproduce it, and an acceptance check. List External groups in a short ignore or filter table with the reason for each.