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
Example: Nodinite Alarm Queue alert in the Nodinite Dashboard, indicating pending entries requiring administrative attention.
What is an Alarm Queue Entry?
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.
Typical workflow:
- Alert fails to send
- Entry is added to the Alarm Queue
- System retries sending periodically
- Success: Entry is removed
- Failure: Entry remains, administrator notified
Diagram: Visualizes the typical workflow for Nodinite Alarm Queue Entries, showing the retry logic and administrative notification.
Managing Alarm Queue Entries
Administrators can manage the Alarm Queue using the following actions:
- Purge Queue: Remove all entries at once using the 'Purge' button (confirmation required)
- Remove Entry: Delete individual entries via the 'Actions' button and 'Remove entry' menu item (confirmation required)
- View Details: Click an entry to see all information needed to resend the alert, including last attempt output and metadata
All sensitive operations are fully audited by Nodinite.
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 Step
Alarm Plugins - Overview
Alarm Queue -Overview
Edit Alarm Plugins