- 0 minutes to read

Managing the Nodinite Event Log Alarm Plugin

Gain full control and visibility over your integration landscape with the Nodinite Event Log Alarm Plugin. This feature empowers you to send real-time, actionable alerts directly to the Windows Event Log, enabling seamless integration with monitoring tools like SCOM and MOM. Ensure compliance, traceability, and rapid incident response for your business-critical systems.

On this page, you will learn how to:

✅ 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 for compliance and traceability
✅ Streamline incident response with automated, real-time notifications

Send Nodinite alerts directly to the Windows Event Log for robust monitoring, compliance, and integration with third-party tools.

Diagram: How Nodinite alerts flow to the Windows Event Log and integrate with third-party monitoring tools.

The Nodinite Event Log Alarm Plugin sends alerts triggered by the Monitoring Service from Monitor Views to the Windows Server Event Log (Application). This enables seamless integration with monitoring tools like SCOM, MOM, or any third-party solution that reads Windows Event Logs.

Example: Windows Event Log entries from the Nodinite Event Log Alarm Plugin.

The Event Log Alarm Plugin comes pre-installed with Nodinite Core Services.

Configuring the Event Log Alarm Plugin

Configure the Alarm Plugin using the Nodinite Web Client by navigating to "Administration" > "Settings" > "Alarm Plugins" and selecting "Event Log". See Add or manage Alarm Plugin for generic details.

Within the Configuration tab, you will find two sub-tabs:

Example: Configuration tabs for the Event Log Alarm Plugin.

Basic tab

From the Basic tab, enter the essential information for the plugin:

Property	Description	Link
Web Client URL	Base URL for the Web Client (used to generate a link to the Monitor View that originated the alert)
Event Id	The Event Id to use when writing events to the Windows Application Event Log (0-65535). Variables can be used, e.g., `{Alarm.JsonPath:MonitorViews[0].Integrations[0].CustomMetaDatas[?(@.Name=='SLA')].CustomValues[0].Value}`. Default is EventId=0 for configuration errors or invalid dynamic variables.
Event Source	See the Variables user guide for more info. Variables can be used, e.g., '`Nodinite: [{Customer} \| {Environment}]`'

Example: Basic tab configuration.

Write options tab

From the Write options tab, configure the following properties:

	Option	Description
	Split by Resource	When checked, each resource is written as a separate log event. NOT DEFAULT
✅	Write event on evaluated state = 'OK'	Checked if alarms for Monitor Views with state change to 'OK' should be written to the event log
	Write event on evaluated state = 'Warning'	Checked if alarms for Monitor Views with state change to 'Warning' should be written to the event log
	Write event on evaluated state = 'Error'	Checked if alarms for Monitor Views with state change to 'Error' should be written to the event log
	Write event on evaluated state = 'Unavailable'	Checked if alarms for Monitor Views with state change to 'Unavailable' should be written to the event log
	Write event on evaluated state = 'Connection Error'	Checked if alarms for Monitor Views with state change to 'Connection Error' should be written to the event log

Specific Settings in Monitor Views ^{New 7.x}

From any Monitor View where the Event Log Alarm Plugin is used, you can create reusable alarm entries that override the global settings. Each alarm entry inherits settings from the global Event Log plugin and allows you to customize specific sections using override checkboxes.

Example: Monitor View-specific Event Log alarm entry showing override options.

Override Basic Options

Check the Override Basic options checkbox to customize basic settings for this specific alarm entry.

Example: "Override Basic options" checkbox at the top of the Basic tab.

When override checkbox is CHECKED:

Property	Description
Web Client URL	Custom URL for the Web Client (used to generate a link to the Monitor View)
Event Id	Custom Event Id for this alarm entry (0-65535). Variables can be used.
Event Source	Custom Event Source name. Variables can be used.

Override Monitoring State Options

Check the Override Monitoring state options checkbox to customize which monitoring states trigger alarms for this specific entry.

Example: "Override Monitoring state options" checkbox. When checked, customize which states trigger event log entries.

When override checkbox is CHECKED:

Trigger on changed Resource state – Send alarm when individual resource changes state (vs Monitor View state)
Write event on OK – Write to event log when Monitor View enters OK state
Write event on Warning – Write to event log when Monitor View enters Warning state
Write event on Error – Write to event log when Monitor View enters Error state
Write event on Unavailable – Write to event log when Monitor View enters Unavailable state
Write event on Connection Error – Write to event log when Monitor View enters Connection Error state

Override Recurrence

Check the Enable Recurrence checkbox to configure recurring event log entries for ongoing issues.

Example: Recurrence override settings for the Event Log Alarm Plugin.

When override checkbox is CHECKED:
Configure different recurrence intervals for each monitoring state (OK, Warning, Error, Unavailable, Connection Error) to ensure persistent problems are logged at regular intervals.

Learn more about configuring recurrence intervals →

Change Stylesheet

Select a custom Stylesheet to format the event log entry content for this alarm entry.

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 alert here.

With Nodinite, you gain traceability, compliance, and seamless integration with your existing monitoring infrastructure—empowering your team to respond quickly and confidently to any event.