Sentry Errors to GitHub Issues
Review production errors from Sentry and optional Axiom logs, group related failures, and prepare prioritized GitHub issues with source links. Check the first report before enabling a recurring triage workflow.
What Okou 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 Okou can generate from Sentry and Axiom.
Agent summary
Okou 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. Review production errors from Sentry and optional Axiom logs, group related failures, and prepare prioritized GitHub issues with source links. Check the first report before enabling a recurring triage workflow.
Why manual error triage creates alert fatigue
Production errors arrive across monitoring tools, while the issue tracker holds the work already in progress. Okou groups the available evidence, checks existing issues, and prepares a prioritized first pass. Review the first report, then configure the schedule and the issue writes your team wants.
How Okou automates daily error triage
1. Choose the accounts and access
2. Start in the Okou conversation
3. Review and reuse the workflow
Sentry, GitHub, and Axiom integrations for error triage
This workflow is a Sentry GitHub integration with an agent in the middle: Okou 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 Okou reads
RequiredOkou 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. Okou never resolves, merges, or reassigns your Sentry issues, and the record it writes goes to GitHub instead.
GitHub integration: the issues Okou files
RequiredAfter you authorize issue creation, each selected error becomes a GitHub issue in the repository you point Okou 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. Okou applies the labels you specify and proposes an owner only when the repository or your instructions establish one. 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 Okou cross-references
OptionalAxiom is optional and it earns its place on deduplication. If your log management already runs on Axiom, Okou 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.
Okou vs. manual triage vs. Sentry alert rules
Daily error triage is the first layer of automated incident response. Teams automate Sentry to GitHub with Okou, 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.
Okou's Sentry workflow automation
Okou groups errors, cross-checks available logs, and proposes issues with source evidence. After the first review, configure the recurring workflow’s thresholds, repository mapping, and permitted writes. Ownership stays unassigned when the evidence is insufficient.
Tips for better results
Frequently asked questions
How to triage Sentry errors and turn them into GitHub issues?
Connect Sentry and GitHub, choose the production project and repository, and request a first triage report. Review the grouped errors and proposed issues, then authorize selected issue creation or define the recurring workflow’s write scope.
How to deduplicate errors across Sentry and Axiom?
Yes. Okou 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 Okou run error triage after every deploy?
Yes. A supported GitHub workflow-completion or webhook trigger can start triage after a verified production deployment. Configure the workflow, branch, completion state, and observation window. A merge to main alone is not evidence of a deployment.
Which tools does the error triage automation need?
Sentry supplies the error data and GitHub receives the issues you authorize. Axiom is optional for additional log context. Start with a report before enabling issue writes.
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 Okou, and revoking one leaves the others untouched.
Can Okou file issues in more than one GitHub repository?
Yes. Tell Okou 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 Okou change anything in Sentry?
No. The Sentry integration is read-only here: Okou 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 Okou creates is the GitHub issue.
Run your first Sentry triage
Start in the Okou conversation with your sources and the result you need. Review the first result, then decide which parts to save as a workflow.
