- 5 minutes to read

Monitor View External Notifications Tab

The External Notifications tab is the third of four tabs when you add or manage a Monitor View. It decides which Alarm Plugins push alerts outside Nodinite when the Monitor View changes state: email, interactive email, the Windows Event Log, or a webhook into Teams, Slack, or your ticketing system. Because Nodinite alerts on the state of the whole view, not on every Resource change, one problem gives one alert plus the reminders you configure.

Select Alarm Plugins

💡Configure alerts to tell the world when there's a change and need to know

Select one or more Alarm Plugin entries to push alerts outside Nodinite. Since 7.2.0, a Monitor View holds no alarm settings; the selected entries hold them (Add or manage Alarm Plugin).

Monitor View External notifications tab with the Alarm Plugins panel listing the selected Email options entry (7.10)
Click Edit in the Alarm Plugins panel to add or remove entries; the minus icon removes one.

graph LR subgraph "App Server" roMS(fal:fa-watch-fitness Monitoring Service) end subgraph "Alert recipients" roMS -.->|"Send Alert"| roMail(fal:fa-envelope Mail) roMS -.->|"Send Alert"| roTicket(fal:fa-bug Issue Tracking System) roMS -.->|"Send Alert"| roEventLog(fal:fa-list Event Log) end style roMS fill:#E47528,color:#fff style roMail fill:#9E59BB,color:#fff style roTicket fill:#9E59BB,color:#fff style roEventLog fill:#9E59BB,color:#fff

The Monitoring Service (orange) pushes alerts from the Monitor View to the recipients of each selected Alarm Plugin (purple).

Out-of-the-Box Plugins

Assign Alarm Plugins to Monitor View dialog with the four default entries and the Email options entries created by the migration (7.10)
The Assign Alarm Plugins to Monitor View dialog lists every Alarm Plugin entry: the four defaults (Email, Email options, Event Log, Webhook) and the entries the 7.2.0 migration created per Monitor View. Check the entries to use and click Confirm and close.

Recurrence and the alert layout (Stylesheets) are set on the entry. For different settings, select another entry.

Note

The Nodinite Monitoring Service is responsible for making you aware. Nodinite is Always Aware.

How Nodinite's Smart Alert Triggering Works

Nodinite takes a fundamentally different approach to alerting compared to traditional monitoring products. Understanding this philosophy helps you configure alerts effectively and reduces alert fatigue.

The Traditional Problem

Many monitoring products trigger an alert for every single resource state change. In production environments, this can easily produce hundreds of thousands of alerts:

  • A dead letter queue with 1 message triggers an alert
  • The same queue with 99 messages triggers another alert
  • When it reaches 1,001 messages, yet another alert fires

The Nodinite Approach

Nodinite uses Monitor View-level triggering as the intelligent control point:

  1. Monitor View State Drives Alerts - If all resources in a Monitor View are OK, the Monitor View state is now OK
  2. First Problem Triggers Alert - When Nodinite detects the first resource in error state, the Monitor View changes to error and triggers the alert
  3. Additional Resources Extend Alert - If another resource also turns into error (or any other state), this triggers a new alert (configurable via recurrence settings)
  4. Focus on What Matters - Whether there's 1 dead letter message or 1,001, the fact remains: there's already a problem you should solve

Business Benefits

  • Reduced Noise - No alert storms from the same ongoing issue
  • Focused Response - Team responds to the problem, not individual state changes
  • Intelligent Escalation - Configure recurrence intervals to remind without overwhelming
  • Cost Efficiency - Less time filtering false alerts, more time solving real problems

Example Scenario

Without Nodinite (traditional approach):

  • 10:00 AM: Alert - Queue has 1 message in error
  • 10:05 AM: Alert - Queue has 50 messages in error
  • 10:10 AM: Alert - Queue has 200 messages in error
  • Result: 3 alerts for the same problem, team wastes time correlating

With Nodinite (intelligent approach):

  • 10:00 AM: Alert - Monitor View "Production Orders" changed to Error state
  • 10:15 AM: Reminder alert (recurrence configured for every 15 minutes)
  • Result: Clear problem identification, team focuses on root cause

This approach keeps the noise down and helps you focus on what's important and what's not.

Configuring Alert Recurrence

When you enable recurrence on an Alarm Plugin entry, Nodinite resends alerts at regular intervals for ongoing issues. This ensures persistent problems don't go unnoticed.

Enable Recurrence

Check Enable Recurrence on the Recurrence tab of the Alarm Plugin entry (Add or manage Alarm Plugin); it applies to every Monitor View that selects the entry.

Enable Recurrence checkbox with Ok, Warning, Error, Connection Error, and Unavailable Time Interval selectors
Recurrence configuration panel showing interval selection for each monitoring state (OK, Warning, Error, Unavailable, Connection Error) to control alert reminder frequency.

Configure Time Intervals by State

For each monitoring state, select a Time Interval that defines how often alerts should be resent while the Monitor View remains in that state:

State Configuration
✅ OK Time Interval Select the Time Interval to use for resending alarms in the OK state
⚠️ Warning Time Interval Select the Time Interval to use for resending alarms in the Warning state
❌ Error Time Interval Select the Time Interval to use for resending alarms in the Error state
🚫 Unavailable Time Interval Select the Time Interval to use for resending alarms in the Unavailable state
Connection Error Time Interval Select the Time Interval to use for resending alarms in the Connection Error state

Tip

  • ❌ Error alerts every 15 minutes - Critical errors need immediate attention
  • ⚠️ Warning alerts every 1 hour - Warnings can wait longer between reminders
  • ✅ OK alerts every 4 hours - Confirmation of resolution sent periodically

This helps prioritize critical issues without overwhelming recipients with notification fatigue.

Example Configuration

Priority Interval Rationale
❌ Error Every 15 minutes Critical - immediate escalation
⚠️ Warning Every 1 hour Important - periodic reminder
✅ OK Every 4 hours Confirmation - reassurance

Note

You must have Time Intervals configured in Nodinite before you can use them for recurrence. Time Intervals are managed in Administration → Customize → Time Intervals, see Time Intervals - Overview.

Next Steps