- 4 minutes to read

Alarm Queue Entry Overview

Make sure every alert reaches its recipients. The Alarm Queue page lists the alerts the Nodinite Monitoring Service could not deliver through an Alarm Plugin, shows why, and lets an administrator fix the cause, delete an entry, or purge the queue.

  • ✅ One list of every undelivered alert, with retries and the last exception
  • ✅ Jump straight to the failing Alarm Plugin and fix it
  • ✅ Copy the error and the JSON payload for support tickets
  • ✅ Delete single entries or purge the queue, always audited

New to the concept? Read What is an Alarm Queue Entry? first.

The Alarm Queue in the Settings menu is where a Nodinite administrator manages all Alarm Queue Entries. The queue should be empty: when it isn't, Nodinite shows a Critical errors detected banner to all users, because people may not be notified when Monitor Views change state.

Understanding the Alarm Queue

graph LR MS["fa:fa-watch-fitness Monitoring Service
state change in a Monitor View"] --> AP["fa:fa-plug Alarm Plugin
Email, Webhook, Event Log ..."] AP -->|"delivered"| OK["fa:fa-check Alert delivered"] AP -->|"failed"| Q["fa:fa-inbox Alarm Queue entry"] Q -->|"retry per AlarmQueueSettings"| AP Q -->|"administrator fixes the plugin,
deletes, or purges"| Admin["fa:fa-user-gear Administrator
this page"] style MS fill:#2678BD,color:#fff style AP fill:#3F827B,color:#fff style OK fill:#93d16d,color:#000 style Q fill:#c33d34,color:#fff style Admin fill:#E47528,color:#fff

Green: delivered alerts never reach the queue. Red: failed deliveries wait in the Alarm Queue and are retried as set in AlarmQueueSettings. Orange: the administrator resolves what retries can't.

The Alarm Queue list

Column Meaning
Edit Opens the Alarm Plugin that failed, so you can fix its configuration; also shows when the entry was Created and Changed
Retries How many send attempts the Monitoring Service has made, and how long ago the last one was
Last Exception The error from the last attempt, with a Copy button; it tells you whether the problem is a configuration error or temporary
JSON Data The size of the alert payload, with a Copy button for the complete JSON
Action Menu with Delete for this entry

Alarm Queue page with the Critical errors detected banner, the Purge Queue button, and one entry with retries, last exception, and JSON data
A webhook that returns 404 Not Found is a configuration error: fix the Alarm Plugin rather than waiting for more retries.

Manage Alarm Queue Entry

The following actions are available for managing Alarm Queue Entries:

  • Delete an individual Alarm Queue Entry
  • Purge all Alarm Queue Entries
  • Filter the list by typing characters in the filter text box
  • Sort by clicking a column header
  • Edit the Alarm Plugin that fails to send the alert
  • Copy the error details or the complete JSON payload of the alert, for support tickets or other documentation

Single Alarm Queue entry with Edit, retries, last exception, Copy buttons, and the Action menu
Each entry carries everything needed to understand and resend the alert.

Delete Alarm Queue Entry

To delete an individual Alarm Queue Entry, open the menu from the Action button and select Delete.

Delete menu item in the Action button menu of an Alarm Queue entry
Delete removes only this entry; the alert is not sent.

In the dialogue, either confirm or abort the requested action.

Confirmation dialog for deleting an Alarm Queue entry
The removal is recorded in Log Audit Search.

Purge Alarm Queue

To remove all entries from the Alarm Queue, click the Purge Queue button. You must confirm your intent before the operation is performed.

Purge Queue button above the Alarm Queue list
Purge only after you've fixed the cause, or the next failing alert lands in the queue again.

In the dialogue, either confirm or abort the requested action.

Confirmation dialog for purging all Alarm Queue entries
Purged entries are gone for good; their alerts are not sent.

Every delete and purge is audited; use Log Audit Search to see who removed what and when.

Frequently Asked Questions / Troubleshooting

You can view, purge, and delete Alarm Queue Entries using the Nodinite Web Client.

How do I resolve entries in the Alarm Queue?

  1. Identify the root cause of the alert failure by reviewing the Last Exception.
  2. Correct any misconfigurations in the Alarm Plugin or the target service. The Alarm Plugins troubleshooting guide covers common Email, DNS, and TLS problems.
  3. Once the issue is resolved, the Monitoring Service automatically retries sending the alert, up to the retry limit set in AlarmQueueSettings (MaxRetries, default 3; 0 retries forever).
  4. If the entry persists, you can manually delete it from the queue.

An expected alert is missing from a Monitor View's history. Where do I look?

Start in the Alarm Queue, then see 'Missing entries in the Distributed Notifications history?'.

Next Steps