Alert shelving can temporarily pause notifications, reminders, updates and escalation for one active alert group without hiding its technical state or service impact.
Responders can shelve and unshelve alerts from the web interface, browser push, Slack, Telegram and Mattermost, with automatic expiry, resumed delivery and complete timeline and audit records.
A native Azure Monitor integration accepts Common Alert Schema webhooks, maps Fired and Resolved events, normalizes Sev0-Sev4 priorities and exposes Azure metadata for routing.
Incoming child-alert event history can use full, initial-only or disabled storage globally, while Event Orchestration can override the mode for matching events without removing operational timeline entries.
OIDC and SAML providers can map identity claims to Slack, Telegram and Mattermost user IDs, making interactive notification actions easier to provision through SSO.
Resource deletion and recreation are safer: dependent routing and scheduler work is disabled consistently while historical records remain available.
The interface adds complete Spanish and Simplified Chinese localizations.
Helm deployments gain custom CA support and safer private-network outbound HTTP configuration, with fixes for numeric values and reverse-proxy static paths.
Configurable retention policies can automatically remove old resolved alert history, Explain Traces and Event Orchestration execution traces in bounded scheduler batches.
Event Orchestration can set full, compact or disabled processing traces per matching event, with bounded buffering and visible compact or truncated state.
Acknowledging a correlated incident now cancels stale notification, reminder and escalation work; same or lower-priority children stay acknowledged while higher-priority events can reopen the group.
A native New Relic integration receives Alerts Workflow issue notifications and routes normalized lifecycle events through standard IncidentRelay intake tokens.
A native Nagios Core and Nagios XI integration maps host and service problems, recoveries and acknowledgements while ignoring downtime, flapping and custom notifications.
The Helm chart is now published to GHCR as an OCI artifact, with hardened defaults and improved SQLite-safe deployment checks.
Dark-theme styling is more consistent across core views, and the Orchestration simulator presents results in a clearer, friendlier format.
Event Orchestration adds global and service-scoped, versioned rules that can normalize, enrich, route, group and deduplicate incoming events before the alert lifecycle finishes processing them.
Rules can select teams, routes, services and policies, change priority and severity, suppress notifications, delay or drop events, and queue secure asynchronous webhooks.
A visual builder and JSON editor are backed by validation, simulation, replay, shadow execution, traces, metrics and immutable publish-and-rollback workflows for safer rollouts.
A native Uptime Kuma integration turns monitor state changes into routed alerts and automatically resolves them when monitors recover.
Silences and maintenance windows can now apply retroactively to unresolved alerts; affected alerts can be reactivated when suppression ends, while escalation and notification state is kept consistent.
The interface adds a dark theme, saved UI preferences, an audit-log view and complete French localization.
Personal API tokens gain granular scopes, while login throttling, safer outbound HTTP requests and stricter validation strengthen the security boundary.
A bundled Helm chart adds a supported path for deploying the web app and background workers to Kubernetes.
PostgreSQL migrations now resolve tables, columns and indexes against the schema selected by the active search path, fixing upgrades that use a non-public schema.
Shared schema-aware introspection helpers are used across legacy migrations and schema checks, avoiding unsafe fallback to the public schema.
Migration upgrades and rollbacks now keep schema changes and migration records in the same database transaction, reducing the risk of partially applied migrations.
New migration tests cover custom PostgreSQL schemas, missing relations, index lookup, database proxies and non-PostgreSQL behavior.
IncidentRelay now includes UI localization support with English, Russian and German catalogs across alert, service, route, rotation, profile and administration workflows.
Grafana OnCall and PagerDuty migration tools help teams move existing on-call data into IncidentRelay.
PagerDuty Events API v2-compatible and Datadog webhook integrations expand the supported alert sources.
Slack Socket Mode support enables Slack app interactions without exposing a public inbound Slack endpoint.
Channel configuration secrets are masked more consistently in API and UI responses.
Official IncidentRelay container images are now published to GitHub Container Registry, and Docker Compose uses the versioned release image by default.
The Helm chart now ships as version 1.1.0 and uses the official IncidentRelay image for Kubernetes deployments.
Audit records, validation errors and readiness responses now redact secrets and avoid exposing sensitive input or database details.
Repeated acknowledge and resolve actions are idempotent, preventing duplicate timeline events, notifications and impact updates.
Service links and runbooks now validate external URLs before rendering actionable links.
Heartbeats add dead-man-switch monitoring for watchdogs, backups, ETL jobs, log shippers and other systems where silence is the failure mode.
Interval and scheduled-completion modes can create normal routed IncidentRelay alerts when expected pings stop arriving.
Heartbeat alerts use the existing route, escalation, notification, maintenance and service-impact pipeline, with optional auto-resolve when pings return.
Business Services and Service Catalog impact scoring now handle status, priority, severity and dependency weights more granularly.
Dependency-aware correlation links related active alert groups across service dependencies.
Possible root causes, symptoms and downstream impact include a confidence score, dependency depth and explanation.
Correlation appears in alert lists, details, timelines and notification context while remaining advisory: alerts are not merged, suppressed or resolved automatically.
Per-dependency settings and propagation delays control correlation timing and noise.
Service Impact History stores scheduled or manual point-in-time snapshots of affected services, alert impact, dependency impact, root causes and blast radius.
Historical charts show affected-service trends and impact reasons, while rankings identify services that are repeatedly affected.
Service reliability analytics combine current SLI/SLO health with historical impact data for operational reviews and incident investigation.
Service context management now provides clearer switching and editing workflows for links, runbooks and dependencies.
Service Notification Policies select shared delivery channels through ordered rules based on alert matchers and event types, with route-only, service-policy and combined delivery modes.
Priority Policies automatically assign P1-P5 using ordered matcher rules, team defaults or service overrides, configurable update modes and source or fallback priorities.
Reusable Matcher Presets and a shared editor bring consistent JSON validation, formatting and suggestions from recent alerts to routes, service rules, silences, policies and service runbooks.
Responders can reset a manually assigned incident priority to automatic management, while Alert Explain Trace shows how priority was selected and applied.
Email, Slack, Mattermost, Telegram and browser push notifications can link directly to the original source event, with improved Sentry event and project detection.
Alert Explain Trace records how incoming alerts are processed, including route matching, grouping, maintenance and silence decisions, notification scheduling and stopped processing paths.
Integration ingest responses now include a trace_id, making routing failures, suppressed incidents and orphan resolved alerts easier to investigate from the UI or API.
The Alerts page includes an Explain view and deep links for opening traces directly from trace_id query parameters.
The Alerts API now validates list queries through a dedicated schema, improving multi-value filters, pagination, sorting and assigned-to-me query behavior.
LibreNMS API Transport alerts can now be received through a dedicated librenms integration endpoint with normalized status, severity, labels, deduplication and recovery handling.
Users can set a profile timezone preference, improving alert and calendar time rendering for distributed teams.
The Notification Center exposes pending responder requests and user-facing incident actions through a dedicated API.
Services API documentation now covers inventory, match rules, links, runbooks, dependencies, impact and analytics endpoints in one dedicated reference.
The Alerts page can preserve filter state and includes an assigned-to-me filter for faster personal triage.
A Helm chart is now available for Kubernetes deployments, including web, scheduler and Telegram worker components, rendered config secrets, probes, ingress, service account and persistence values.
Services can define default stakeholders that are copied into new incidents, so owners and observers can receive created, priority, status and resolved notifications.
Incident responder requests now feed a notification center where targeted users can see pending requests and accept or decline them from the incident workflow.
Incident and service APIs now cover responders, stakeholders, priorities, services and service owner/default stakeholder management.
Incident priorities now use a consistent P1 Critical through P5 Informational scale across alert details and operational views.
The Alerts page supports priority filtering and sorting, while the dashboard shows priority badges and a priority distribution summary.
Incoming alert severity can automatically assign or raise incident priority without overwriting a manually selected priority or lowering an existing automatic priority.
Email, Mattermost, Telegram and browser push notifications now include incident priority, and manual priority changes can notify subscribed stakeholders by email.
Read-only CalDAV sync exposes accessible team on-call schedules to Apple Calendar, Thunderbird, DAVx5 and other compatible clients.
Tokenized ICS subscription feeds let teams add on-call schedules to Outlook, Google Calendar and other calendar clients, with controls to regenerate or revoke feed URLs.
A new signed Sentry integration receives issue alerts, metric alerts and issue lifecycle events, with route-level secrets, deduplication and automatic resolve handling.
Route setup now provides source-specific webhook URLs, token details and ready-to-copy curl examples.
Health and readiness endpoints support Kubernetes probes and load balancer checks.
Maintenance Windows can target groups, teams, services or routes and suppress notifications, suppress new incidents, create maintenance incidents or pause escalations.
Maintenance schedules support timezones, effective statuses and recurring RFC5545 rules.
Responders can create, edit and delete investigation comments directly on alert groups, with actions reflected in the alert timeline.
Alert details now include incident management controls for priority, responder requests and stakeholder notification preferences.
Group managers can manage team users within their access scope.