- 3 minutes to read

Nodinite Alarm Queue Entries – Never Lose a Critical Alert

New 7.x
Nodinite Alarm Queue Entries ensure your organization never loses a critical alert, even if network issues or service outages occur. This page explains how the Alarm Queue delivers resilience, empowers administrators, and keeps your integration monitoring reliable and auditable.

  • ✅ Resilient alert delivery—no lost notifications
  • ✅ Automatic retry and queue management
  • ✅ Full audit trail for all sensitive operations
  • ✅ Empowered administration with actionable insights

Critical errors detected banner on the Dashboard saying Nodinite is unable to send one or more alerts
Every user sees this banner on the Dashboard while the Alarm Queue holds entries; View opens the Alarm Queue.

What is an Alarm Queue Entry?

The Monitoring Service sends alerts through Alarm Plugins (Email, HTTP Webhook, Event Log, and more) when a Monitor View changes state. Earlier versions of Nodinite sent alerts directly, risking loss if the target service was unavailable or network issues occurred. With Nodinite version 7, every unsent alert is added to the Alarm Queue. The system periodically retries sending queued alerts, ensuring maximum reliability for your integration monitoring.

Each Alarm Queue Entry contains:

  • The alert payload and metadata (JSON format)
  • Output from the last send attempt (updated after each retry)
  • A log of all attempts in the Notifications history
  • Actions for administrators to manage the entry

If there are entries in the Alarm Queue, Nodinite displays a visible alert for all users, signaling the need for administrative attention.

Why Use Nodinite Alarm Queue Entries?

  • Ensure no alert is ever lost—even during outages
  • Provide administrators with actionable information and retry options
  • Maintain compliance and auditability for all sensitive operations
  • Empower incident management with detailed entry views and history

Alarm Queue Entries are business critical—system administrators must resolve issues promptly to maintain operational integrity.

How Do Alarm Queue Entries Work?

When an alert cannot be sent, Nodinite adds it to the Alarm Queue. The system periodically reprocesses the queue, attempting to resend each alert. If successful, the entry is removed automatically. Each attempt is logged for transparency and auditing.

If the alert cannot be sent due to misconfiguration or permanent service changes, administrators must manually remove the entry.

The AlarmQueueSettings System Parameter sets how many times the Monitoring Service retries a queued alert (MaxRetries, default 3; 0 retries forever) and how long one send attempt may take (TimeoutSeconds, default 120). When the retries are used up, the entry stays in the queue until an administrator resolves it.

Typical Workflow

graph TD A["fa:fa-bell Alert fails to send"] --> B["fa:fa-inbox Entry is added to the Alarm Queue"] B --> C["fa:fa-rotate System retries sending periodically"] C -->|"Success"| D["fa:fa-check Entry is removed"] C -->|"Failure, retries used up"| E["fa:fa-triangle-exclamation Entry remains,
banner shown to all users"] E -->|"administrator fixes the plugin,
deletes, or purges"| F["fa:fa-user-gear Resolved by administrator"] style A fill:#FFD525,color:#000 style B fill:#E47528,color:#fff style C fill:#2678BD,color:#fff style D fill:#93d16d,color:#000 style E fill:#c33d34,color:#fff style F fill:#3F827B,color:#fff

Yellow: the failed send. Orange and blue: queued and retried automatically. Green: delivered on a retry. Red: needs an administrator, who resolves it in the Alarm Queue (teal).

Managing Alarm Queue Entries

Administrators can manage the Alarm Queue using the following actions:

  • Purge Queue: Remove all entries at once using the Purge Queue button (confirmation required)
  • Delete Entry: Delete individual entries via the Action button menu (confirmation required)
  • View Details: Review the retries, last exception, and JSON payload needed to resend the alert, and open the failing Alarm Plugin to fix it

See the Alarm Queue overview for the step-by-step guide.

All sensitive operations, including removing entries and purging the queue, are fully audited by Nodinite. Use Log Audit Search to find out who removed an entry and when.

If an expected alert is missing from the Distributed Notifications history of a Monitor View, start here; see 'Missing entries in the Distributed Notifications history?'.

The Bottom Line

Nodinite Alarm Queue Entries deliver resilience and reliability for your integration monitoring.
Never lose a critical alert—empower your team to respond, audit, and resolve incidents with confidence.

Next Steps