{"id":182633,"date":"2026-07-13T22:53:42","date_gmt":"2026-07-13T20:53:44","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/pervyj-stabilnyj-vypusk-incidentrelay-sistemy-dlya-organizaczii-dezhurstv-i-marshrutizaczii-opoveshhenij"},"modified":"2026-07-13T22:53:42","modified_gmt":"2026-07-13T20:53:44","slug":"pervyj-stabilnyj-vypusk-incidentrelay-sistemy-dlya-organizaczii-dezhurstv-i-marshrutizaczii-opoveshhenij","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/pervyj-stabilnyj-vypusk-incidentrelay-sistemy-dlya-organizaczii-dezhurstv-i-marshrutizaczii-opoveshhenij","title":{"rendered":"The first stable release of IncidentRelay, a system for organizing on-call duties and alert routing","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

After five months of development, the release of IncidentRelay 1.1 is now live. This project enhances an open system for organizing on-call shifts, routing notifications, and incident management, which can be launched on a self-hosted server. IncidentRelay 1.1 is marked as the first stable release (the 1.0 branch was in beta). The project is aimed at SRE, DevOps, and infrastructure teams that need a locally deployable alternative to SaaS services for on-call management, escalation policies, and incident response. The project code is written in Python and is distributed under the MIT license. <\/p>\n

IncidentRelay receives events from monitoring systems, maps them to services, teams, and rotations, and then delivers notifications to responsible on-call staff or teams. The system features on-call schedules, rotations, shift overrides, incident acknowledgment states (ACK\/Resolve), reminders, escalations, temporary replacements for on-call staff, scheduled maintenance timing, and suppression of noisy alerts. <\/p>\n

The main advantage of the project is complete control over the infrastructure and routing logic. IncidentRelay is deployed in its own environment, works with its own database, and allows for a clear separation of incoming routes, commands, rotations, and delivery channels. Incoming tokens belong to routes, not channels, making it easier to understand which external source has the right to send events to a specific command. <\/p>\n

IncidentRelay supports receiving events from Prometheus Alertmanager, Grafana Alerting, Zabbix, Sentry, LibreNMS, RMON, AWS SNS\/CloudWatch, and arbitrary webhooks. Notification channels include Mattermost, Slack, Telegram, Discord, Microsoft Teams, email, webhooks, browser\/PWA push, and voice call providers. In Mattermost and Telegram, notifications can contain actions for acknowledgment and resolution, allowing incidents to be handled without switching to a separate interface. <\/p>\n

The project can be launched via Docker Compose, an RPM package for Red Hat-based distributions, manually through systemd, or in Kubernetes using a Helm chart. For smaller installations, SQLite can be used, while for production systems and higher loads, PostgreSQL is recommended. <\/p>\n

The new version includes the following changes: <\/p>\n