Alarm Plugin Overview
Take full control of your Alarm Plugins in Nodinite with a single, intuitive overview. This page shows you how to add, edit, delete, restore, and manage Alarm Plugins—empowering you to deliver reliable, automated alerts and notifications for your integration environment.
✅ Centralized management of all Alarm Plugins
✅ Fast add, edit, delete, restore, and filter options
✅ Automated, flexible alerting for integration monitoring
✅ Secure, role-based administration in the Web Client
Get started now: How to Add or Manage Alarm Plugin user guide
The Alarm Plugin Overview in the Settings main menu is where a Nodinite Administrator centrally manages all Alarm Plugins for your integration environment. This unified view streamlines configuration, maintenance, and troubleshooting—empowering you to deliver reliable, automated alerts and notifications.
Within the Alarm Plugin Overview, you'll find a sortable list of all currently installed Alarm Plugins. For large environments, quickly narrow down the list using the filter text box. This makes it easy to locate, review, and manage plugins at scale.
Example: List of defined Alarm Plugins.
Manage Alarm Plugin
The following actions are available for managing Alarm Plugins:
- Add new Alarm Plugin
- Edit Alarm Plugin
- Delete Alarm Plugin
- Filter the list of Alarm Plugins
- Sort
Add new Alarm Plugin
To add a new Alarm Plugin, review the Troubleshooting user guide for step-by-step instructions.
Edit Alarm Plugin
To edit an existing Alarm Plugin, simply click the link in the Name column or open the menu from the "Actions" button and select "Edit".
Example of the 'Edit' menu item in the Actions button.
Delete Alarm Plugin
To delete an existing Alarm Plugin, open the menu from the 'Actions' button and select 'Delete'.
Example of the 'Delete' menu item in the 'Actions' button.
In the dialogue, either confirm or abort the requested action.
Example of the confirmation dialog when deleting an Alarm Plugin.
Restore deleted Alarm Plugin
To restore a deleted Alarm Plugin, first check the "Include deleted Alarm Plugins" checkbox.
When checked, deleted Alarm Plugins are included in the list.
Example of a deleted Alarm Plugin in the list.
Then open the menu from the "Actions" button and select "Restore".
Click the 'Restore' menu item to restore a deleted Alarm Plugin.
In the dialogue, either confirm or abort the requested action.
Example of the confirmation dialog when restoring a deleted Alarm Plugin.
Common Alarm Plugin Scenarios
These scenarios show how organizations configure Alarm Plugins for multi-channel alerting, escalation workflows, custom integrations, and operational efficiency.
Scenario 1: Multi-Channel Alert Escalation
Challenge: Critical production monitors need tiered escalation—Slack for initial alert, email after 5 minutes, SMS after 15 minutes if unacknowledged.
Solution: Configure multiple Alarm Plugins with delayed execution for escalation workflow.
Implementation: Create three Alarm Plugins: (1) Slack plugin (immediate), (2) Email plugin (5-minute delay), (3) SMS plugin (15-minute delay). Assign all three to critical production Monitor Views. When monitor fails, Slack notifies immediately → Team has 5 minutes to respond → Email escalates → Final SMS escalation if still unresolved.
Business Benefit: Reduces mean time to response (MTTR) by 60%, prevents alert fatigue through graduated escalation, ensures critical issues never missed.
Example: Payment API fails at 2 AM → Slack alert wakes on-call engineer → Engineer acknowledges within 3 minutes → Email and SMS suppressed → Issue resolved → Escalation prevented unnecessary wake-ups for entire team.
Scenario 2: Custom ServiceNow Integration for Incident Ticketing
Challenge: Enterprise uses ServiceNow for incident management. Manual ticket creation from Nodinite alarms creates delays and human error.
Solution: Configure custom HTTP Alarm Plugin posting to ServiceNow REST API.
Implementation: Create HTTP POST Alarm Plugin with ServiceNow endpoint URL, authentication headers, and JSON payload template using Stylesheet transformation. Map monitor fields to ServiceNow incident fields (severity, category, description, assignment group). When alarm triggers, automatically create ServiceNow incident with proper routing.
Business Benefit: Eliminates manual ticket creation, reduces incident creation time from 5 minutes to 10 seconds, ensures complete alarm context captured in ticket, improves SLA compliance.
Example: Production integration fails → Nodinite alarm triggers → HTTP plugin creates ServiceNow incident INC0012345 → Incident auto-assigned to Integration Operations team → Team receives notification with Nodinite link → Investigation begins within 2 minutes.
Scenario 3: Business-Hours-Only Email Alerts
Challenge: Development environment monitors trigger frequent non-critical alarms overnight. Email flood during off-hours creates alert fatigue and reduces response to genuine production issues.
Solution: Configure time-based Alarm Plugin filtering for business hours only.
Implementation: Create two Email Alarm Plugins: (1) "Production-24x7-Email" (no time restrictions), (2) "Development-Business-Hours-Email" (active only Mon-Fri 8AM-6PM). Assign production Monitor Views to 24x7 plugin, development views to business-hours plugin. Development alarms suppressed overnight, production alarms always sent.
Business Benefit: Reduces off-hours email noise by 90%, improves on-call engineer sleep quality, ensures production alarms stand out, maintains development monitoring coverage during business hours.
Example: Dev environment database connection fails at 11 PM → Alarm triggers but email suppressed (business hours only) → Same failure at 9 AM → Email sent immediately → Developer investigates during work hours → Issue resolved.
Scenario 4: Webhook Integration with Microsoft Teams Channels
Challenge: Operations team uses Microsoft Teams for collaboration. Want Nodinite alarms posted to dedicated Teams channels with rich formatting and actionable links.
Solution: Configure HTTP Alarm Plugin with Teams webhook connector and adaptive card formatting.
Implementation: Create Teams Incoming Webhook connector for "Integration-Alerts" channel. Configure HTTP Alarm Plugin with Teams webhook URL. Use Stylesheet to transform alarm object into Teams Adaptive Card JSON format (title, severity color coding, monitor details, quick action buttons). Assign plugin to Monitor Views.
Business Benefit: Centralizes operational communication in Teams, enables team collaboration on alarm resolution, provides one-click access to Nodinite for investigation, improves team visibility into integration health.
Example: Order processing monitor fails → Teams channel receives rich card with red severity indicator → Card shows: "Order-API monitor critical since 14:23" → Team members discuss in thread → Developer clicks "View in Nodinite" button → Opens monitor in browser → Executes Remote Action to restart service → Posts resolution update in Teams thread.
Frequently Asked Questions / Troubleshooting
You can create, edit, and delete Alarm Plugins using the Nodinite Web Client.
How do I create a new Alarm Plugin?
Read and follow the instructions in this user guide: 'Add or Manage Alarm Plugin'.