Automated Error Triage, Done Before Standup
Zero is an AI DevOps agent that automates daily error triage. Every morning, it pulls unresolved errors from Sentry and Axiom, deduplicates them across both sources, and files assigned GitHub issues with full stack traces before standup, saving engineers 20 to 30 minutes of manual review.
What Zero delivers: a daily error triage report
Explore a sample AI-generated error triage report with prioritized incidents, cross-source deduplication, assigned GitHub issues, severity, volume, and time saved. The data is illustrative; the report format is a real output Zero can generate from Sentry and Axiom.
Agent summary
Zero inspected 17 raw errors from Sentry and Axiom, deduplicated them into 13 root causes, created 6 assigned GitHub issues, and routed 2 watch-only signals to #dev.
- Raw errors inspected
- 1712 Sentry · 5 Axiom
- Unique root causes
- 13after deduplication
- GitHub issues created
- 6all assigned
What is error triage?
Error triage, also called bug triage or incident triage, is the process of grouping, prioritizing, and assigning production errors so engineers know what to fix first. Zero acts as an AI SRE agent across Sentry, Axiom, and GitHub: it deduplicates errors, applies thresholds, attaches stack traces, and assigns code owners. The result is a consistent daily error triage automation with less alert fatigue.
Why manual error triage creates alert fatigue
Every morning, an engineer has to open Sentry, scan unresolved Sentry alerts, cross-check Axiom, identify what is new or duplicated, decide what is serious, open GitHub issues, and find the right owner. That repetitive first pass costs 20 to 30 minutes of focused engineering time and creates alert fatigue before real work starts. Zero runs at 8:45 AM and completes the same triage before anyone opens a laptop.
How Zero automates daily error triage
Step 1: Connect your tools
Step 2: Ask Zero
Step 3: Take it further
Sentry, GitHub, and Axiom integrations for error triage
This workflow is a Sentry GitHub integration with an agent in the middle: Zero reads from Sentry, cross-checks the same window in Axiom, and writes to GitHub. Each connector is granted separately and scoped to what the workflow actually uses, so read access to your error data never implies write access to your repositories.
Sentry integration: the errors Zero reads
RequiredZero reads your Sentry error tracking through the Sentry issues API, querying unresolved errors in the environments you name, sorted by frequency. For each one it reads the title and culprit, the event count and number of users affected, the level, and the first- and last-seen timestamps, then pulls the latest event for the full stack trace and its release and environment tags. That covers what the triage decision needs: what broke, how often, where, and since when. In this workflow the Sentry integration is read-only. Zero never resolves, merges, or reassigns your Sentry issues, and the record it writes goes to GitHub instead.
GitHub integration: the issues Zero files
RequiredEvery error that clears your threshold becomes a GitHub issue in the repository you point Zero at. The issue carries the error title, the stack trace, the occurrence and affected-user counts, the first- and last-seen timestamps, and a link back to the Sentry issue so the original data stays one click away. Zero applies the labels you specify and assigns the code owner for the files named in the stack trace. Write access is scoped to the repositories you grant, and issue creation is all it does: no commits, no pull requests, no repository settings.
Axiom integration: the Axiom logs Zero cross-references
OptionalAxiom is optional and it earns its place on deduplication. If your log management already runs on Axiom, Zero reads it in the same pass: it runs an APL query against the datasets you choose, bounded to the same time window as the Sentry pull, and matches those Axiom logs against the error signatures it already has. That catches the case where one failure surfaces twice in different formats, and it adds the request-level context around the failure that a Sentry event alone does not carry. Without Axiom the workflow still runs end to end, and deduplication falls back to Sentry data only.
Zero vs. manual triage vs. Sentry alert rules
Daily error triage is the first layer of automated incident response. Teams automate Sentry to GitHub with Zero, completing the repetitive first pass before a problem needs broader AI incident management.
Manual triage
An engineer reviews Sentry and Axiom, identifies duplicates, decides severity, opens issues, and finds an owner. It is flexible, but repeats the same 20 to 30 minutes of work every morning.
Sentry alert rules
Rules notify the team when a threshold is crossed. They are useful for detection, but the team still has to correlate logs, deduplicate errors, create GitHub issues, and assign owners.
Zero's Sentry workflow automation
Zero runs the Sentry automation end to end: query, cross-source deduplication, thresholding, issue creation, stack-trace attachment, and code-owner assignment. On-demand and post-deploy runs use the same workflow.
Tips for better results
Frequently asked questions
How to triage Sentry errors and turn them into GitHub issues?
To automatically create GitHub issues from Sentry, connect Sentry and GitHub to Zero, then give it a schedule or an on-demand prompt. Zero queries unresolved errors, applies occurrence and environment filters, creates one issue per qualifying error, attaches the stack trace and timestamps, and assigns a code owner.
How to deduplicate errors across Sentry and Axiom?
Yes. Zero compares error signatures, stack traces, messages, and timing across Sentry and Axiom, then merges matching events into one triage record. Each underlying source remains linked for investigation.
How to reduce alert fatigue from error monitoring?
Limit triage to production, set an occurrence threshold, deduplicate the same error across tools, and route low-volume errors to a summary instead of creating an issue. This keeps the queue focused on errors that need action.
Can Zero run error triage after every deploy?
Yes. Create an automation that starts the error triage workflow after a deploy or merge to main, optionally waits for a short observation window, then checks Sentry for new production errors and files qualifying issues.
Which tools does the error triage automation need?
Sentry and GitHub are required: Sentry supplies the error data and GitHub receives the assigned issues. Axiom is optional, but it adds log context and improves cross-source deduplication.
What permissions does the Sentry GitHub integration need?
Sentry needs read access to issues and events in the projects you triage. GitHub needs issue-write access on the repositories that should receive the issues. Axiom, if you use it, needs query access to the datasets you name. You grant each connector separately in Zero, and revoking one leaves the others untouched.
Can Zero file issues in more than one GitHub repository?
Yes. Tell Zero which service or project maps to which repository and it routes each issue accordingly, so frontend errors land in your web repo and API errors in your backend repo. That mapping lives in the prompt, so you can change it without reconfiguring the GitHub connector.
Does Zero change anything in Sentry?
No. The Sentry integration is read-only here: Zero queries issues and events and writes nothing back. Your issue states, assignments, and resolution history stay exactly as your team left them. The only thing Zero creates is the GitHub issue.
Run your first Sentry triage
Connect Sentry, GitHub, and optionally Axiom. Use the same daily triage prompt to see the workflow in action without rebuilding it by hand.