Alarm Plugin Overview
Take full control of your Alarm Plugins in Nodinite from a single overview. This page shows how alerts travel from a Monitor View to your team, how Alarm Plugin entries work, and how to find, add, and manage them.
✅ Alarm Plugin entries – Shared alarm configurations that many Monitor Views select New 7.2.0
✅ Inheritance model – An added entry overrides only what differs and inherits the rest from the plugin's default entry New 7.2.0
✅ Centralized management – Update one entry; every Monitor View that selects it follows
✅ Reduced administration – No more duplicating settings across dozens of Monitor Views
✅ Automated migration – Former Monitor View-specific configurations became entries on upgrade New 7.2.0

Animated walkthrough: the Alarm Plugins list with one row per entry and the Monitor Views that use it, including the four default entries (Email, Email options, Event Log, and Webhook). The entry Contoso: Ops e-mail opens on its General tab, where Control runs alarm tests and the Monitor Views card lists where it is used. Back in the list, its Action menu > Show in Mapify draws the entry with its Monitor Views and their Roles and users in Mapify.
Get started now: How to Add or Manage Alarm Plugin user guide
The Alarm Plugin Overview in the Settings menu is where a Nodinite Administrator centrally manages all Alarm Plugins for your integration environment. End users never configure Alarm Plugins; they see the resulting states in their Monitor Views.
Understanding the Alert Flow
The Monitoring Service evaluates the Resources in each Monitor View. When the Monitor View, or a Resource in it, changes state, the Monitoring Service hands the alert to every Alarm Plugin entry the Monitor View has selected. Each entry is built on one of the four Alarm Plugins and formats the message with a Stylesheet. If delivery fails, the alert waits in the Alarm Queue and is retried as set by the AlarmQueueSettings System Parameter. During Maintenance Mode, alerts are held back until the window ends.
state change"] ms["fa:fa-watch-fitness Monitoring Service"] entry["fa:fa-plug-circle-bolt Selected
Alarm Plugin entry"] target["fa:fa-paper-plane Email, Event Log,
or HTTP Webhook"] queue["fa:fa-bell Alarm Queue
retry"] ok --> mv warn --> mv err --> mv mv --> ms ms -->|"Monitor View selects entry"| entry entry -->|"Delivered"| target entry -->|"Delivery failed"| queue queue -->|"AlarmQueueSettings"| entry style ok fill:#93d16d,color:#000 style warn fill:#E47528,color:#fff style err fill:#c33d34,color:#fff style mv fill:#2678BD,color:#fff style ms fill:#2678BD,color:#fff style entry fill:#2678BD,color:#fff style target fill:#93d16d,color:#000 style queue fill:#c33d34,color:#fff
How an alert travels: an OK (green), Warning (orange), or Error (red) state change in a Monitor View reaches the Monitoring Service (blue), which calls each entry the Monitor View has selected. A delivered alert ends green; a failed one goes red to the Alarm Queue and is retried.
Alarm Plugin Entries (Nodinite 7.2.0)
Nodinite 7.2.0 remade the Alarm Plugin concept. Before, each Monitor View could hold its own "specific configuration" of a plugin, so changing a recipient in 10 Monitor Views meant 10 edits. Now the settings live in Alarm Plugin entries:
- Each of the 4 plugins (Email, Email with Options, Event Log, HTTP Webhook) has a default entry with the base settings.
- You add more entries on any plugin; each added entry overrides selected tabs and inherits the rest from the default entry.
- A Monitor View selects which entry or entries it uses.
Email with Options"] def["fa:fa-star Default entry
Email options"] ent["fa:fa-envelope Added entry
Support Team Email"] mvA["fa:fa-display 10 Monitor Views"] mvB["fa:fa-display Other Monitor Views"] plugin -->|"ships with"| def plugin -->|"type of"| ent def -.->|"inherited tabs"| ent mvA -->|"select"| ent mvB -->|"select"| def style plugin fill:#2678BD,color:#fff style def fill:#3F827B,color:#fff style ent fill:#E47528,color:#fff style mvA fill:#9E59BB,color:#fff style mvB fill:#9E59BB,color:#fff
A plugin (blue) ships with a default entry (teal); an added entry (orange) inherits the tabs it doesn't override. Monitor Views (purple) select entries; changing "Support Team Email" once updates all 10 Monitor Views.
Example Scenario
- Before 7.2.0: Send support alerts to
support@contoso.comin 10 Monitor Views → changing toicc@contoso.comrequires editing all 10 Monitor Views - Since 7.2.0: Add one entry "Support Team Email" and select it in the 10 Monitor Views → update once, all 10 follow
Think of entries as alarm channels, as in other monitoring products. The plugin pages describe every tab: Email, Email with Options, Event Log, and HTTP Webhook.
Automated Upgrade Migration
When you upgrade to Nodinite 7.2.0 or later, every former Monitor View-specific configuration becomes its own entry, built on the same plugin and selected by that Monitor View. Your alerts continue working exactly as before. Afterwards, you may have duplicate entries (for example 10 entries that all send to support@contoso.com); consolidate them into one shared entry, select it in those Monitor Views, and delete the rest. This one-time cleanup doesn't apply to fresh installations.
Alarm Plugin List
The Alarm Plugins page ("Alarm Plugins distribute Alerts from Monitor Views") lists the four default entries and every entry added with Add Alarm or by the 7.2.0 migration.

The Contoso: Ops e-mail entry, of type Email options, lists the Monitor Views that use it; one of them has a "Deleted" badge.
Narrow down the list with:
- Filter the result – "Type characters to filter and narrow the result set"
- Select a Monitor View – "Filter by Monitor View", to see only the entries a Monitor View uses
- Include deleted – "Include deleted Alarm Plugins" (Show deleted records)
Understanding the List Columns
| Column | Description |
|---|---|
| Name | Entry name; click to edit. Default entries carry the plugin name (Email, Email options, Event Log, Webhook). Sort also by Created or Changed |
| Type | The Alarm Plugin type (Email, Email options, Event Log, Webhook) |
| Monitor Views | The Monitor Views that use the entry; click one to open it. A deleted Monitor View shows a "Deleted" badge |
| Description | Short description; click more to read all of it |
| Action | Edit, Show in Mapify, Show in Mermaid, Delete or Restore, and Permanently Delete |
Manage Alarm Plugin Entries
- Add Alarm – Add an entry on any of the four plugins (steps)
- Edit – Click the name, or choose Edit in the Action menu
- Show in Mapify / Show in Mermaid – See the entry and its Monitor Views in Mapify Rendering (needs a Mapify license) or Mermaid Rendering
- Delete / Restore – Soft delete, and undo it
- Permanently Delete – Hard delete, enabled only after every Monitor View has been removed from the entry

Permanently Delete appears on a deleted entry, once no Monitor View uses it.
Every menu item, its dialogs, and the success messages are described in The Action Menu.
Alarm Plugin Comparison
Choose the right alarm plugin for your monitoring strategy. Each plugin offers distinct authentication methods, Stylesheet support, and use cases.
| Feature | E-mail with Options | Event Log | HTTP Webhook | |
|---|---|---|---|---|
| Authentication Options | • SMTP Basic (username/password) • Anonymous relay (IP whitelist) |
• SMTP Basic (username/password) • OAuth 2.0 - Client Credentials New 7.x • Anonymous relay (IP whitelist) |
• None (Windows integrated security) • Monitoring Service runs with appropriate permissions |
• None (public endpoints) • Basic (username/password) • OAuth 2.0 - Client Credentials New 7.x • HTTP headers (e.g., x-api-key) • Optional proxy |
| Stylesheet Type | XSLT (default) or Liquid | XSLT (default) or Liquid | Liquid (default) or XSLT | None (JSON payload only) |
| Primary Use Case | Simple email notifications • Basic alerts to users with email addresses • Limited customization • Legacy support |
Advanced email alerting • Rich HTML formatting with XSLT • Per-state monitoring (OK, Warning, Error) • Custom recipients per Alarm Plugin entry • Alert recurrence configuration • Recommended for most scenarios |
Windows Event Log integration • SCOM/MOM integration • Compliance and audit requirements • 3rd party event log readers • Custom event IDs and sources |
External system integration • Jira, ServiceNow, Freshdesk tickets • Azure Logic Apps, Power Automate • Custom API endpoints • Incident management automation • Rich Custom Metadata in JSON payload |
| Alert Recurrence | ✅ Yes | ✅ Yes | ✅ Yes | ✅ Yes |
| Custom Metadata in the alert | ✅ Full access via the Stylesheet | ✅ Full access via the Stylesheet | ✅ Full access via the Stylesheet | ✅ Full JSON payload |
| Typical Scenarios | • Small teams with basic needs • Legacy integrations • Quick setup without customization |
• Operations teams requiring detailed alerts • Distribution lists with rich formatting • Executive summaries with SLA data • Multi-state monitoring (OK confirmations) |
• Enterprise monitoring (SCOM/MOM) • Compliance-driven organizations • Centralized Windows event management • Security information and event management (SIEM) |
• DevOps teams using Jira/ServiceNow • Automated ticket creation • Business process automation • Multi-system orchestration • Data warehouse integration |
| Configuration Complexity | Simple | Moderate | Simple | Advanced |
| Recommended For | Quick start - Get alerts flowing fast | Production use - Most common choice for email alerts | Enterprise monitoring - Integrate with existing monitoring infrastructure | Automation - Trigger actions in external systems |
Custom Metadata on your Integrations and Resources travels with every real alert (alarm tests carry none), so responders see the owner, SLA, and runbook (Custom Metadata in alerts).
Choosing the Right Alarm Plugin
Use this decision tree to select the appropriate alarm plugin:
Need email alerts?
- Yes → Go to step 2
- No → Go to step 3
Email requirements:
- Simple text alerts to users → Use E-mail
- Rich HTML formatting, custom recipients, per-state configuration → Use E-mail with Options (recommended)
- Modern authentication (OAuth 2.0) → Use E-mail with Options New 7.x
Need Windows Event Log integration?
- Yes (SCOM/MOM/SIEM) → Use Event Log
- No → Go to step 4
Need external system integration?
- Yes (Jira, ServiceNow, Logic Apps, Teams, etc.) → Use HTTP Webhook
- Anything else → Use the HTTP Webhook and put your own logic in the receiving endpoint. Nodinite 7 loads only the four built-in Alarm Plugins; custom Alarm Plugins aren't supported.
Tip
Multi-channel alerting: A Monitor View can select several Alarm Plugin entries. For example:
- E-mail with Options for operations team (rich HTML, per-state)
- HTTP Webhook for Jira ticket creation (automation)
- Event Log for SCOM integration (enterprise monitoring)
This ensures critical issues reach your team through multiple channels while automating incident management workflows.
Frequently Asked Questions / Troubleshooting
You create, edit, and delete Alarm Plugins in the Nodinite Web Client. More answers are in the Alarm Plugin troubleshooting guides.
How do I create a new Alarm Plugin?
Read and follow the instructions in this user guide: 'Add or Manage Alarm Plugin'.
Why didn't my alert arrive?
Check the Alarm Queue first: alerts that could not be delivered wait there with the error. Then check the Monitor View's alert history (Distributed Notifications), and whether a Maintenance Mode window was active. Common causes are SMTP, DNS, and certificate problems; see the troubleshooting guides.
Which ports does the Monitoring Service need for Alarm Plugins?
The SMTP and HTTPS ports are listed in the Monitoring Service firewall settings.
Next Steps
Related Topics
- What is an Alarm Plugin?
- E-mail - Simple email alerts
- E-mail with options - Advanced email alerts with rich formatting
- Event Log - Windows Event Log integration for SCOM/MOM
- HTTP Webhook - External system integration (Jira, ServiceNow, Logic Apps)
- Alarm Queue - Alerts waiting for delivery
- AlarmQueueSettings - Retries and timeout for queued alerts
- Monitoring Service - Raises the alerts
- Stylesheets - Format alert content
- Time Intervals - Configure alert recurrence intervals
- Monitor Views
- User Notifications - Maintenance Mode
- Access Management
- Show who to call in alerts