- 9 minutes to read

Variables and JSON Path examples for Alerts

Unlock the full power of dynamic, actionable notifications in Nodinite by leveraging built-in variables and JSONPath expressions. This guide shows you how to extract Repository Model data and tailor email and event log content for advanced integration monitoring.

  • ✅ Personalize alerts with dynamic variables and JSONPath
  • ✅ Extract actionable data from Repository Model for notifications
  • ✅ Automate and customize email and event log content
  • ✅ Empower rapid response and compliance for integration teams

The Subject of an E-mail with options Alarm Plugin set to Customer, Environment, StatusAndCount and DateTime variables and saved, a Monitor View alert after the Print Spooler stops, and the received e-mail with the resolved subject IBSS DEV: 1 Warning at a date and time, animated walkthrough (7.12)
Animated walkthrough: on the Configuration tab of an E-mail with options entry, under Basic, set the Subject to {Customer} {Environment}: {StatusAndCount} at {DateTime} and Save. When the Monitor View Contoso: Alert variables sends its alert, the e-mail arrives with the subject IBSS DEV: 1 Warning at 2026-11-17 04:35:21.

Control the content in email and Windows Event Log entries using variables and JSONPath for maximum flexibility and actionable insights.

With Nodinite, you can dynamically generate alert content at run-time using built-in variables (like the customer name from CustomerName and the environment name from EnvironmentName) and data from the Repository Model, such as Custom Metadata on Integrations. This enables you to deliver highly relevant, context-rich notifications to your team and stakeholders—empowering rapid response and compliance.

Typical use cases include:

  • Email Plugins (E-mail and E-mail with options)
    • Subject – Personalize subject lines with dynamic data for clarity and traceability. All the variables below work here, and in the Recurrence subject of E-mail with options.
  • Event Log
    • Event Source – Default: Nodinite: [{Customer} | {Environment}]. Takes only {Customer}, {Environment}, and {Alarm.JsonPath:…}.
    • EventId (0-65535) – A fixed number or {Alarm.JsonPath:…}. The result is 0 when it isn't a whole number from 0 to 65535, also when the JSONPath finds nothing or several values.

Variables work nowhere else: the HTTP Webhook has none (it posts the whole alarm object), and Stylesheets receive the alarm object itself.

Variables

Variable name Description Example Works in
{Customer} Customer name of the Nodinite installation (CustomerName) Contoso Subject, Event Source
{Environment} Environment name of the Nodinite installation (EnvironmentName, shown in the Web Client) Prod/Test/QA... Subject, Event Source
{Version} The Nodinite version of the Monitoring Service 7.12.0.0 Subject
{Status} The states of the Monitor Views in the alert, without counts, joined with a comma; plural when more than one view has the state Errors, OK Subject
{StatusAndCount} The same states with the number of Monitor Views (not Resources) in each 2 Errors, 1 OK Subject
{DateTime} When the alarm was created, in the local time of the Monitoring Service server, as yyyy-MM-dd HH:mm:ss 2026-11-17 04:35:21 Subject
{Alarm.JsonPath:...} Advanced: Use JSONPath to extract Repository data from the alarm object sent to the Alarm Plugin See JSONPath examples below Subject, Event Source, EventId

A subject is one line (line breaks become spaces) of at most 998 characters. A trial installation adds - Nodinite Trial expires … to it.

Windows Event Log Application entry with the Source Nodinite: IBSS | DEV, Level Warning, and Event Id 4350, read with Get-WinEvent (7.12)
The Application log entry on the Monitoring Service server: the Event Source Nodinite: [{Customer} | {Environment}] resolved to Nodinite: [IBSS | DEV], and the Event Id taken from the Monitor View's id.

The Event Log Alarm Plugin entry with Event Source Nodinite: Customer | Environment and an Event Id from the JSONPath of the Monitor View id, saved, then the Print Spooler stops and the Application log entry on the Monitoring Service server shows the resolved source and Event Id 4350, animated walkthrough (7.12)
Animated walkthrough: on the Event Log entry Contoso: Event Log with variables, set Event Source to Nodinite: [{Customer} | {Environment}] and Event Id to {Alarm.JsonPath:MonitorViews[0].MonitorViewId}, and Save. The next alert writes an Application log entry with the source Nodinite: [IBSS | DEV] and Event Id 4350, the Monitor View's id.

Important

From the Event Source, only the characters &, <, and > are removed; every other character is kept. A source that doesn't exist yet is created in the Application log the first time it is used, which needs local administrator rights for the Monitoring Service account.

JSONPath Examples

Any valid JSONPath on the Alarm (JSON) object sent by the Monitoring Service can be used to set run-time values for Subject, Event Source, and EventId. Several matches are joined with a comma, a date is written as ISO 8601, and a path that matches nothing is left as you typed it. For example:

  • Monitor View Name – {Alarm.JsonPath:MonitorViews[*].Name}
  • Monitor View Id, for an EventId – {Alarm.JsonPath:MonitorViews[0].MonitorViewId}
  • Repository Model Data ('Integration Number' is an example Custom Metadata field name)
{Alarm.JsonPath:MonitorViews[0].Integrations[0].CustomMetaDatas[?(@.Name=='SLA')].CustomValues[0].Value}
{Alarm.JsonPath:MonitorViews[0].Integrations[0].CustomMetaDatas[?(@.Name=='Integration Number')].CustomValues[0].Value}

The Subject set to Customer, Environment and Status plus the JSONPath of the first Integration's SLA, saved, then the OK alert after the Print Spooler starts again and the received e-mail with the subject IBSS DEV: OK, SLA Silver, animated walkthrough (7.12)
Animated walkthrough: the Subject {Customer} {Environment}: {Status}, SLA {Alarm.JsonPath:MonitorViews[0].Integrations[0].CustomMetaDatas[?(@.Name=='SLA')].CustomValues[0].Value} reads the SLA of INT002: Invoices, the Integration assigned to the Monitor View. When the Print Spooler runs again, the OK alert arrives as IBSS DEV: OK, SLA Silver.

JSON Alarm Example

Here is an example of an Alarm (JSON) object to apply your JSONPath expressions on. The HTTP Webhook receives the same object as its payload; the email plugins' Stylesheets receive it as XML (Alarm Plugin Object). Each changed Resource carries its agent as Source, its own CustomMetaDatas, and WasRemovedFromMonitorView; each Monitor View has Users, the recipients, filled for the plugins that send to users. Created is in UTC.

{
	"MonitorViews": [{
		"MonitorViewId": 1,
		"Name": "Test View",
		"Description": "Simple unit testing view.",
		"WebSite": null,
		"StatusCode": {
			"StatusCode": 0,
			"Name": "OK"
		},
		"NumberOfMonitoredResources": 2,
		"Users": [],
		"Integrations": [{
			"IntegrationId": 1,
			"Name": "INT001 - Orders to first company",
			"Description": "",
			"WebSite": "https://www.nodinite.com",
			"CustomFields": [{
				"CustomFieldId": 1,
				"Name": "SLA",
				"Description": "",
				"WebSite": null,
				"ValueType": {
					"CustomFieldTypeId": 1,
					"Name": "Text",
					"Description": null,
					"WebSite": null
				},
				"CustomValues": [{
					"CustomValueId": 1,
					"Value": "1",
					"Description": "Act fast!!",
					"WebSite": "https://www.nodinite.com",
					"ValueType": {
						"CustomFieldTypeId": 1,
						"Name": "Text",
						"Description": null,
						"WebSite": null
					}
				}]
			}],
			"CustomMetaDatas": [{
				"CustomMetaDataId": 1,
				"Name": "Summary",
				"Description": "My integration is the perfect one",
				"WebSite": "https://www.nodinite.com",
				"DataType": 1,
				"CustomValues": [{
					"CustomValueId": 1,
					"Value": "My integration is the perfect one",
					"Description": "Act fast!!",
					"WebSite": "https://www.nodinite.com",
					"ValueType": null
				}]
			}]
		}],
		"ChangedResources": [{
			"ResourceId": 1,
			"Name": "First Resource - Send Port",
			"Description": null,
			"WebSite": "https://www.nodinite.com/resource/send-port",
			"Source": {
				"SourceId": 1,
				"Name": "Test Monitoring Agent Configuration",
				"Description": "Simple Monitoring Agent Configuration for testing purposes only.",
				"Server": null,
				"Environment": null,
				"Version": null,
				"WebSite": "https://www.nodinite.com/"
			},
			"Category": {
				"CategoryId": 1,
				"Name": "Send Ports",
				"Description": "Send ports category.",
				"WebSite": null
			},
			"Application": {
				"ApplicationId": 1,
				"Name": "BizTalk System",
				"Description": "Default BizTalk application",
				"WebSite": "https://www.nodinite.com/application/biztalk-system"
			},
			"StatusCode": {
				"StatusCode": 0,
				"Name": "OK"
			},
			"LogText": "All OK!",
			"CustomMetaDatas": [],
			"WasRemovedFromMonitorView": false
		},
		{
			"ResourceId": 2,
			"Name": "Second Resource - Receive Port",
			"Description": null,
			"WebSite": null,
			"Source": {
				"SourceId": 1,
				"Name": "Test Monitoring Agent Configuration",
				"Description": "Simple Monitoring Agent Configuration for testing purposes only.",
				"Server": null,
				"Environment": null,
				"Version": null,
				"WebSite": "https://www.nodinite.com/"
			},
			"Category": {
				"CategoryId": 2,
				"Name": "Receive Ports",
				"Description": "Receive ports category.",
				"WebSite": "https://www.nodinite.com/category/receive-ports"
			},
			"Application": {
				"ApplicationId": 1,
				"Name": "BizTalk System",
				"Description": "Default BizTalk application",
				"WebSite": "https://www.nodinite.com/application/biztalk-system"
			},
			"StatusCode": {
				"StatusCode": 0,
				"Name": "OK"
			},
			"LogText": "All OK!",
			"CustomMetaDatas": [],
			"WasRemovedFromMonitorView": false
		}]
	},
	{
		"MonitorViewId": 2,
		"Name": "Second View",
		"Description": "Simple test view (second).",
		"WebSite": null,
		"StatusCode": {
			"StatusCode": 2,
			"Name": "ERROR"
		},
		"NumberOfMonitoredResources": 2,
		"Users": [],
		"Integrations": [],
		"ChangedResources": [{
			"ResourceId": 10,
			"Name": "LogAPI Queue",
			"Description": "Queue for Nodinite LogAPI.",
			"WebSite": null,
			"Source": {
				"SourceId": 2,
				"Name": "MSMQ",
				"Description": "Monitoring Agent Configuration to monitor MSMQ queues.",
				"Server": "NODINITE-DEV01",
				"Environment": "Production",
				"Version": "1.0",
				"WebSite": null
			},
			"Category": {
				"CategoryId": 10,
				"Name": "MSMQ Queue",
				"Description": "MSMQ Queues category",
				"WebSite": "https://msdn.microsoft.com/en-us/library/ms711472%28v=vs.85%29.aspx"
			},
			"Application": null,
			"StatusCode": {
				"StatusCode": 2,
				"Name": "ERROR"
			},
			"LogText": "Number of messages in queue exceeded error limit.",
			"CustomMetaDatas": [],
			"WasRemovedFromMonitorView": false
		},
		{
			"ResourceId": 11,
			"Name": "LogAPI Test Queue",
			"Description": "",
			"WebSite": null,
			"Source": {
				"SourceId": 2,
				"Name": "MSMQ",
				"Description": "Monitoring Agent Configuration to monitor MSMQ queues.",
				"Server": "NODINITE-DEV01",
				"Environment": "Production",
				"Version": "1.0",
				"WebSite": null
			},
			"Category": {
				"CategoryId": 10,
				"Name": "MSMQ Queue",
				"Description": "MSMQ Queues category",
				"WebSite": "https://msdn.microsoft.com/en-us/library/ms711472%28v=vs.85%29.aspx"
			},
			"Application": null,
			"StatusCode": {
				"StatusCode": 1,
				"Name": "WARNING"
			},
			"LogText": "Number of messages in queue exceeded warning limit, but not error limit.",
			"CustomMetaDatas": [],
			"WasRemovedFromMonitorView": false
		}]
	}],
	"Version": "5.0.0.0",
	"Environment": "Test",
	"Customer": "Nodinite",
	"Created": "2019-01-01T01:00:00.000000Z",
	"WebClientUrl": "https://nodinite.contoso.com/",
	"IsRecurring": false,
	"ProductStatus": {
		"IsTrial": false,
		"ExpirationDate": null
	}
}

Next Steps