Managing the Nodinite Event Log Alarm Plugin
Gain full visibility over your integration landscape with the Nodinite Event Log Alarm Plugin. It writes alerts to the Windows Event Log, where monitoring tools like SCOM and MOM pick them up, giving you compliance, traceability, and fast incident response for business-critical systems.
- ✅ Send Nodinite alerts to the Windows Event Log for robust monitoring
- ✅ Integrate with SCOM, MOM, or any third-party event log reader
- ✅ Customize alert content and event properties with variables for compliance and traceability
- ✅ Streamline incident response with automated, real-time notifications
Understanding the Event Log Flow
Application"] ro3rdParty["fa:fa-desktop 3rd party solution
like MOM/SCOM"] ok --> ms warn --> ms err --> ms ms -->|"Monitoring state options filter"| windows ms -->|"Liquid Stylesheet"| windows windows -.->|"optional"| ro3rdParty style ok fill:#93d16d,color:#000 style warn fill:#FFD525,color:#000 style err fill:#c33d34,color:#fff style ms fill:#2678BD,color:#fff style windows fill:#2678BD,color:#fff style ro3rdParty fill:#9E59BB,color:#fff
An OK (green), Warning (yellow), or Error (red) state change reaches the Monitoring Service (blue), which writes the entry to the Windows Event Log when the state is selected on the Monitoring state options tab of the Event Log entry the Monitor View uses; third-party tools (purple) can read it from there.
The Nodinite Event Log Alarm Plugin writes alerts raised by the Monitoring Service for Monitor Views to the Windows Server Event Log (Application) on the server that hosts the Monitoring Service. Monitoring tools like SCOM, MOM, or any third-party solution that reads Windows Event Logs can then act on them.
Each alert becomes an entry with the Event Source and Event Id you configure.
The Event Log Alarm Plugin comes pre-installed with Nodinite Core Services.
Default Entry and Additional Entries
Since Nodinite 7.2.0, every Alarm Plugin is used through Alarm Plugin entries. The Event Log default entry ships with Nodinite; you can add more entries built on the Event Log plugin, for example one Event Source per business area, and each Monitor View selects the entry or entries it uses. The entry concept and the Action menu are described once in Add or manage Alarm Plugin.
Open the default entry from "Administration" > "Settings" > "Alarm Plugins" by selecting "Event Log".
"Writes to the local event log where the Monitoring Service is running." No Monitor View uses this entry yet.
The Configuration tab shows the Alarm Plugin Type and three sub-tabs.
The type can't be changed on a default entry; on an entry you added, changing it resets all configuration settings.
Configuration Tabs
Basic tab
Use a variable in Event Id to give SCOM a different id per SLA level.
| Field | Help text in the Web Client | Notes |
|---|---|---|
| Web Client URL | Write events to the Event Log with a link to the signaling Monitor View. Enter the URL to this Nodinite instance (NOTE: Do not use 'localhost') | The address of your Web Client |
| Event Id | A positive Integer value between 0 and 65535 for the Event Log being written to the Application Event Log. You can use a macro like: | Example: {Alarm.JsonPath:MonitorViews[0].Integrations[0].CustomMetaDatas[?(@.Name=='SLA')].CustomValues[0].Value}. EventId 0 is used for configuration errors or invalid dynamic values |
| Event Source | The name of the 'Event Source'. You can use the macros like: , , . NOTE: '&', '<' or '>' are illegal characters automatically removed by the system | Example: Nodinite: {Customer} \| {Environment}, where {Environment} comes from the EnvironmentName System Parameter |
| Stylesheet (unlabeled list) | Select the Stylesheet to use when formatting the output of the alarm. | Default: Event Log Alarm Plugin, a Liquid Stylesheet |
Monitoring state options tab
Clear Send Alarm on OK if your event log reader shouldn't receive recovery events.
| Field | Help text in the Web Client |
|---|---|
| Trigger on changed Resource state | When checked, trigger an Alarm when any Resource changes its state. Otherwise, trigger an Alarm when the Monitor View changes its monitoring state |
| Split by Resource | When checked, separately write each Resource in the Monitor View to the event log (false is the default) |
| ✅ Send Alarm on OK | When checked, send alarms to the Event Log for Monitor Views changing its state to the 'OK' state |
| ⚠️ Send Alarm on Warning | … to the 'Warning' state |
| ❌ Send Alarm on Error | … to the 'Error' state |
| 🚫 Send Alarm on Unavailable | … to the 'Unavailable' state |
| Send Alarm on Connection Error | … to the 'Connection Error' state |
Split by Resource writes one event per Resource instead of one per Monitor View.
Recurrence tab
Persistent problems are written again at the interval set for their state.
| Field | Help text in the Web Client |
|---|---|
| Enable Recurrence | Configure the recurrence for redistributing alarms |
| ✅ Ok Time Interval, ⚠️ Warning Time Interval, 🚫 Unavailable Time Interval, ❌ Error Time Interval, Connection Error Time Interval | A Time Interval per state; "If needed, you can create or adjust Time Intervals here" opens the Time Intervals page |
Using an Event Log Entry in a Monitor View
A Monitor View doesn't hold its own Event Log settings. On the External notifications tab of the Monitor View, the administrator selects the Event Log Alarm Plugin entry, or several entries, to use. For a different Event Id or Event Source on some Monitor Views, add another Event Log entry, check Override … options on the tabs that differ, and select that entry in those Monitor Views (how).
Execute and Restore Alarm Test
The Control panel buttons write test events to the Application Event Log on the Monitoring Service server (alarm tests).
Animated walkthrough: one test, two entries. The recording reads the log with Get-WinEvent, because a browser can't show Event Viewer.
- Open the default entry Event Log, then Configuration > Basic: here Event Id 4377 and the Event Source.
- Click Execute Alarm test. The result says 2 events were written to the event log.
- On the Monitoring Service server, the Application log has one Error entry for the Monitor View in Error and one Information entry for the OK one, both with Event Id 4377 and the source Nodinite:
| .
Stylesheet
You can fully customize the content written to the Windows Event Log. The Nodinite Event Log Alarm Plugin supports Stylesheets of type Liquid.
Use the JSON below as a template to test your custom Stylesheet:
{
"SplitByResource": false,
"AlarmObject": --- PASTE JSON HERE ---
}
Example: Data structure sent to the Event Log plugin by Nodinite.
You can find an example of the JSON alarm object in the Variables and JSON Path examples for Alerts user guide, and how the data differs between plugins on the Alarm Plugin Object page. If an entry can't be written, check the Alarm Queue.