All Quiet changelog
New Integration: GitHub Two-Way Sync for Incident Management
We created a GitHub integration to support flexible workflows between your code and your on-call alerts. You can now sync GitHub issues and All Quiet incidents in three ways.
Integration Options
Mode | Function | Best For |
|---|---|---|
Outbound | All Quiet creates and updates GitHub issues automatically. | Engineering teams tracking incidents as tickets. |
Inbound | GitHub issues trigger or resolve All Quiet incidents. | Developers who prefer starting workflows in GitHub. |
Two-Way Sync | Real-time synchronization between both platforms. | Hybrid teams using multiple observability tools. |
How it Works
Outbound (All Quiet to GitHub): All Quiet creates a GitHub issues when you forward an incident automatically, manually or via specific routing rules. The system updates the GitHub issues as the incident status changes.
Inbound (GitHub to All Quiet): New GitHub issues trigger All Quiet incidents based on your criteria. You can also configure GitHub to resolve or reopen incidents.
Two-Way Sync: This mode keeps both platforms identical. It ensures your team sees the same data whether they work in GitHub or the All Quiet app.
Why this matters
This update reduces manual work and prevents data silos. By linking GitHub issues directly to our incident management system, your workflows are automized and information is automatically handled in sync across both systems.
Here’s how to set it up: https://docs.allquiet.app/integrations/outbound/github