- 5 minutes to read

Nodinite Alarm Plugins – Stay in Control, Stay Notified

Nodinite Alarm Plugins deliver instant, targeted alerts and notifications to your team, so you never miss a critical integration event. This page explains how Alarm Plugins help you automate incident response, meet compliance needs, and keep your business running smoothly.

✅ Instantly notify the right people about critical events
✅ Integrate with email, webhooks, and event logs for maximum flexibility
✅ Customize alerts to fit your business and compliance needs with Stylesheets
✅ Automate incident management and streamline your workflow
✅ No lost alerts; resilience is built in with the Alarm Queue New 7.1

🔔 Never Miss a Critical Event Again! With Nodinite Alarm Plugins, the right people get the right alerts at the right time.

graph LR roOK["fa:fa-circle-check OK"] roWarn["fa:fa-triangle-exclamation Warning"] roErr["fa:fa-circle-xmark Error"] roMV["fa:fa-display Monitor View"] roMS["fa:fa-watch-fitness Monitoring Service"] roAP["fa:fa-plug-circle-bolt Alarm Plugin"] roUser["fa:fa-users End-Users"] roIncident["fa:fa-ticket Incident tickets"] roQueue["fa:fa-bell Alarm Queue
retry on failure"] roOK --> roMV roWarn --> roMV roErr --> roMV roMV -->|"State change"| roMS roMS -->|"Alert"| roAP roAP -->|"Notifies"| roUser roAP -->|"Creates"| roIncident roAP -.->|"Delivery failed"| roQueue style roOK fill:#93d16d,color:#000 style roWarn fill:#FFD525,color:#000 style roErr fill:#c33d34,color:#fff style roMV fill:#2678BD,color:#fff style roMS fill:#2678BD,color:#fff style roAP fill:#2678BD,color:#fff style roUser fill:#93d16d,color:#000 style roIncident fill:#93d16d,color:#000 style roQueue fill:#c33d34,color:#fff

An OK (green), Warning (yellow), or Error (red) state change in a Monitor View reaches the Monitoring Service (blue), which calls the Alarm Plugin. Delivered alerts reach people and ticket systems (green); failed deliveries wait in the Alarm Queue (red) and are retried.

What is a Nodinite Alarm Plugin?

Every organization has its own processes and workflows. Nodinite Alarm Plugins deliver alerts exactly how and where you need them.

A Nodinite Alarm Plugin is loaded by the Monitoring Service. The Monitoring Service calls the configured Alarm Plugins only after it has decided that a notification should be sent for a Monitor View or an affected Resource.
For example, an email Alarm Plugin may send a notification for a meaningful state change, a configured recovery message, or an add-to-view event that operators should know about.
The System Administrator customizes alerts with a Stylesheet, or a Developer adds custom code in your own Webhook behind the HTTP Webhook plugin.

Why Use Nodinite Alarm Plugins?

✅ Instant Awareness – Get notified as soon as an issue arises.
✅ Full Control – Define custom logic and target the right audience.
✅ Seamless Integration – Works with your existing tools; no need to adapt your processes.
✅ Scalable & Customizable – Configure alarms to fit your exact business needs, with Alarm Plugin entries that any number of Monitor Views can select.

Nodinite Alarm Plugins are designed for maximum flexibility: automate incident response, meet compliance needs, and keep your business running smoothly.

How Do Alarm Plugins Work?

Alarm Plugins deliver the alerts selected by the Monitoring Service. They don't decide on their own when a Monitor View should alert.
For example:

  • A Webhook can notify your incident management system and include Custom Metadata (how metadata enriches alerts). This is ideal for Partner solutions.
  • The Nodinite Email Plugin can send alerts to your team.
  • The Nodinite Event Log Plugin can store notifications for audit and compliance.

What Alarm Plugins Do and Do Not Do

Alarm Plugins do Alarm Plugins do not do
Deliver email, webhook, or event log notifications Create alerts on their own
Format messages with Stylesheets or webhook logic Fan out one Monitor View change to unrelated Monitor Views
Receive alerts after the Monitoring Service has evaluated maintenance and postponement rules Receive empty alerts without affected Resources

During Maintenance Mode, or when postponed Auto Healing is in effect, the plugin is called only when the alert is actually ready to leave Nodinite. When delivery fails, the alert is kept as an Alarm Queue Entry and retried as set by the AlarmQueueSettings System Parameter.

🎯 Our Recommendation:
💡Use the Nodinite HTTP Webhook Alarm Plugin for maximum flexibility and control—tailor alerts to your specific needs effortlessly!

Out-of-the-Box Alarm Plugins

Nodinite provides four ready-to-use Alarm Plugins. Nodinite 7 loads only these four; for anything else, put your own logic behind the HTTP Webhook.

Alarm Plugins list in the Web Client with the Email default entry and an Email options entry linked to Monitor Views (7.10)
The Alarm Plugins list in the Nodinite Web Client shows the default entries and the entries built on them, with the Monitor Views that use each one.

Managing Alarm Plugin Entries

New 7.2.0
Since Nodinite 7.2.0, you use Alarm Plugins through Alarm Plugin entries. Each of the four plugins has a default entry with the base settings. You can add more entries on any plugin, and each Monitor View selects which entry or entries it uses. Change an entry once, and every Monitor View that selects it follows.

graph LR plugin["fa:fa-plug Alarm Plugin
Email, Email with Options,
Event Log, or HTTP Webhook"] def["fa:fa-star Default entry"] add["fa:fa-plus Added entries"] mv["fa:fa-display Monitor Views"] plugin -->|"ships with"| def plugin -->|"type of"| add def -.->|"inherited settings"| add mv -->|"select one or more"| def mv -->|"select one or more"| add style plugin fill:#2678BD,color:#fff style def fill:#3F827B,color:#fff style add fill:#E47528,color:#fff style mv fill:#9E59BB,color:#fff

A plugin (blue) ships with a default entry (teal); added entries (orange) inherit what they don't override. Monitor Views (purple) select the entries they use.

Creating Reusable Alarm Plugin Configurations

Administrators add entries with the Add Alarm button on the Alarm Plugins administration page. This allows you to:

  • Create named configurations for specific teams or scenarios
  • Reuse one configuration across multiple Monitor Views
  • Keep alert settings consistent

Add Alarm button on the Alarm Plugins administration page
The Add Alarm button starts a new Alarm Plugin entry (steps).

Tip

When you upgrade to 7.2.0 or later, every Monitor View that had its own specific settings for one of the 4 plugins gets a new named Alarm Plugin entry with those settings, and the Monitor View selects it. Consolidate identical entries afterwards.

Deleting Alarm Plugin Entries

Delete is a soft delete that you can undo with Restore. Permanently Delete (hard delete) is enabled only after every Monitor View has been removed from the entry. This safeguard prevents accidental removal of entries that are in use.

Action menu with Edit, Show in Mapify, Show in Mermaid, Delete, and a disabled Permanently Delete with its hint (7.10)
"To delete an Alarm Plugin permanently, you must unassign all Monitor Views from it first."

The whole Action menu, including Show in Mapify and Show in Mermaid, is described in Add or manage Alarm Plugin.

The Bottom Line

🔔 Be the first to know when something happens.
⚡ React instantly and prevent costly downtime.
Integrate alerts into your existing workflow effortlessly.

💡Get started with Nodinite Alarm Plugins today—because when every second counts, staying informed is everything!

Next Steps