Search results

High Availability

Status: Open.

Feature

#394 In Icinga/icinga-notifications;

· nilmerg opened on Mar 2, 2026

Support a configurable retention policy for closed incidents

Status: Open.

Task

#393 In Icinga/icinga-notifications;

· nilmerg opened on Mar 2, 2026

Do not persist events any longer to database

Status: Open.

Task

#392 In Icinga/icinga-notifications;

· nilmerg opened on Mar 2, 2026

Reduce data persistence to an absolute minimum

Status: Open.

Feature

#391 In Icinga/icinga-notifications;

· nilmerg opened on Mar 2, 2026

Loosen integration of sources so that a Web counterpart is not mandatory

Status: Open.

Feature

#390 In Icinga/icinga-notifications;

· nilmerg opened on Mar 2, 2026

Let sources automate their initial setup and authentication

Status: Open.

Feature

#389 In Icinga/icinga-notifications;

· nilmerg opened on Mar 2, 2026

Require a secure transport when sources deliver events

Status: Open.

Task

#388 In Icinga/icinga-notifications;

· nilmerg opened on Mar 2, 2026

Http Proxy for Webhook Channels

Status: Open.

#385 In Icinga/icinga-notifications;

· ochnerd opened on Feb 9, 2026

Implement a channel plugin that can wrap existing NotificationCommand scripts

Status: Open.

Task

#384 In Icinga/icinga-notifications;

· julianbrost opened on Jan 22, 2026

Support incoming Prometheus Alert Manager Alerts

Status: Open.

#383 In Icinga/icinga-notifications;

· ShadowJonathan opened on Jan 17, 2026

Conceptual question: What happens if channel plugin reports an error

Status: Open.

#381 In Icinga/icinga-notifications;

· alamp1360 opened on Dec 29, 2025

Feature Request Close Incident manually

Status: Open.

#379 In Icinga/icinga-notifications;

· moreamazingnick opened on Dec 17, 2025