- 8 minutes to read

What is a Monitoring Event?

Track every heartbeat of your integration landscape with Nodinite Monitoring Events. Each event captures a moment in time—a state change, a threshold breach, or a status update—enabling real-time alerts, automated remediation, and comprehensive audit trails for operational excellence.

A Monitoring Event is a logged record of a state change or status update for a monitored Resource. These events are the foundation of Nodinite's proactive monitoring, alerting, and auto-healing capabilities. The Monitoring Service creates them, evaluates them, and purges them after DaysToKeepMonitorEvents days (see Data Retention).

Key Benefits

  • ✅ Real-time state tracking - Capture every change in monitored Resources instantly
  • ✅ Alert automation - Trigger notifications when thresholds are breached
  • ✅ Auto-healing enabled - Events drive automated remediation actions
  • ✅ Historical analysis - Long-term event storage for troubleshooting and compliance
  • ✅ Audit trail - Complete visibility into when, what, and why issues occurred

The Windows Service Print Spooler goes from OK to Warning at the Monitoring Agent's next poll in the Monitor View Contoso: Order fulfilment, then Action, View Resource History opens its Resource History with the new Monitoring Event at the top, animated walkthrough (7.12)
Animated walkthrough: the Windows Service Print Spooler is stopped on the server. At the Monitoring Agent's next poll its Resource turns Warning in the Monitor View on its own, with the Log Text Service is stopped. Action > View Resource History then shows the new Monitoring Event at the top of the list.

The Monitoring Event Lifecycle

graph LR subgraph "Discovery & Monitoring" MA[fal:fa-monitor-waveform Monitoring Agent
Discovers Resources] R[fal:fa-lightbulb-on Resource
Queue, Service, API, DB] MA --> | Monitors | R end subgraph "Event Generation" SC[fal:fa-exchange State Change
OK → Error
Error → OK] ME[fal:fa-chart-line Monitoring Event
Logged with timestamp] R --> | Triggers | SC SC --> | Creates | ME end subgraph "Response" MS[fal:fa-watch-fitness Monitoring Service
Processes events] ALERT[fal:fa-bell Alert
Email, ticket, etc.] HEAL[fal:fa-ambulance Auto Healing
Corrective action] ME --> | Evaluated by | MS MS --> | May trigger | ALERT MS --> | May trigger | HEAL end subgraph "Storage & Analysis" DB[fal:fa-database Log Databases
Historical records] HIST[fal:fa-history History View
Audit trail] ME --> | Stored in | DB DB --> | Powers | HIST end style ME fill:#E47528 style ALERT fill:#c33d34 style HEAL fill:#93d16d style HIST fill:#2678BD

Diagram: From Resource state changes to automated responses—every Monitoring Event flows through Nodinite's intelligent processing pipeline

What Generates a Monitoring Event?

Monitoring Events are created whenever the Monitoring Service detects a change in the evaluated state of a Resource. The following scenarios generate events:

State Transitions

From State To State Event Description Typical Cause
✅ OK ❌ Error Resource failure detected Service stopped, queue full, threshold breached
❌ Error ✅ OK Resource recovered Issue resolved, service restarted
✅ OK ⚠️ Warning Degraded performance detected High queue depth, slow response time
⚠️ Warning ❌ Error Situation worsened Warning threshold exceeded
Any State 🚫 Unavailable Resource cannot be reached Network issue, service offline, misconfiguration
Any State ❌ Connection Error Agent communication failure Monitoring Agent offline, network problem

Non-Event Pattern Monitoring

Some monitoring scenarios generate events when no activity occurs within expected timeframes:

  • File Folder Monitoring - No new files received in expected window
  • Log File Monitoring - No log entries written (indicating stalled process)
  • Scheduled Task - Task did not execute when expected
  • Message Queue - No messages consumed (indicating stalled consumer)

Tip

Non-event monitoring is critical for detecting "silent failures" where systems appear running but aren't processing work.

Monitoring Event Properties

The Resource History page of a Resource shows its Monitoring Events, newest first:

What you see Description
Log Date Time When the Monitoring Service recorded the change
State The new state, shown as the row's colour and icon (OK, Warning, Error, Unavailable, Connection Error)
Log Text The message the Monitoring Agent reported, for example Service is stopped
Error Code The code the Monitoring Agent reported with the state
Resource, Monitoring Agent, Category, Application Shown once at the top of the page, for the Resource the events belong to (Applications, Categories)

The previous state and how long it lasted are not columns: each row's predecessor is the row below it, and the Timeline above the list shows each state's share of the time span.

How Monitoring Events Drive Actions

Monitoring Events are the trigger mechanism for several critical Nodinite features:

1. Alert Distribution

When a Monitoring Event represents a state transition to Warning, Error, Unavailable, or Connection Error, the Monitoring Service evaluates configured Alarm Plugins:

  • Email Alerts - Send notifications to responsible teams
  • Ticket System Integration - Create incidents in ServiceNow, Jira, etc.
  • Event Log - Write entries to the Windows Event Log
  • Webhooks - POST event data to external systems

Alerts are intentionally selective. Nodinite focuses on meaningful state transitions, configured recovery messages, and add-to-view changes that operators should know about. If there is no affected Resource to include, Nodinite skips the alert instead of sending an empty notification.

Important

Some Monitor View membership-only changes may still remain silent today. The most important examples are removals, re-entries caused by exclusion changes, and Resources that start matching an older include filter without a separate state change.

Read more in the 'Alarm Plugins' and 'What is an Alarm Queue Entry' user guides.

2. Auto Healing

Monitoring Events that match Auto Healing configurations trigger automatic Remote Actions:

Depending on your configuration, Nodinite can let Auto Healing act before an alert is sent, so notification delivery may be delayed while the affected Resource is being handled. Typical examples are a stopped Windows Service or a disabled BizTalk Receive Location:

Example Event Auto Healing Response Business Value
Windows Service stopped Execute "Start Service" action Zero-downtime recovery without manual intervention
BizTalk Receive Location disabled Execute "Enable" action Automatic recovery from transient backend issues
Queue depth exceeds threshold Execute "Scale Out" or "Alert Priority Team" Proactive capacity management

Examples of Monitoring Events triggering automated remediation.

Read more in the 'What is Auto Healing' user guide.

3. Historical Analysis

All Monitoring Events are stored in Log Databases for long-term analysis:

  • Troubleshooting - Identify patterns leading to failures
  • Compliance - Audit trail for regulatory requirements
  • Capacity Planning - Analyze trends over weeks/months
  • SLA Reporting - Calculate uptime and availability metrics

The retention period is controlled by the DaysToKeepMonitorEvents System Parameter; see Data Retention.

Read more in the 'Resource State History' user guide (also known as the Event History view).

Viewing Monitoring Events

In Monitor Views

Real-time events are displayed directly in Monitor Views:

Monitor View rows for Non-Events, SQL Statements, Windows Service, Service Bus Queue, and SQL Server Agent Resources in Error, Warning, and OK states, each with its Log Text and Action button (7.12)
Example Monitor View showing Resources with their current states—each state is the result of the most recent Monitoring Event.

A row is not a link. Use Action > Details for what the Monitoring Agent currently reports, and Action > View Resource History (opens in a new tab) for the Resource's Monitoring Events.

In History Views

Historical events can be searched and analyzed:

Resource History page of Print Spooler with the time span, the Timeline, and its Monitoring Events by Log Date Time, Log Text and Error Code, newest first (7.12)
Example Resource State History showing Monitoring Events over time, enabling root cause analysis and pattern detection.

The page shows one Resource and filters on a time span of at most 12 months.

In the Dashboard

The Monitor Views - Health Chart on the Dashboard counts your Monitor Views per state, so a Monitoring Event that changes a Monitor View's state moves it to another slice:

Dashboard Monitor Views - Health Chart counting Monitor Views per state
The Dashboard Health Chart counts Monitor Views per state; it does not list alerts.

Real-World Monitoring Event Scenarios

See how Monitoring Events power operational excellence:

Integration Platform Resource Type Event Trigger Outcome
BizTalk Server Suspended Messages Queue depth > 10 Email alert + Auto-healing resume action
Azure Event Hub Event Hub No messages for 5 minutes Alert to operations team
Windows Server Windows Service Service state: Stopped Auto-healing starts service + Audit log entry
Azure Logic Apps Logic App Disabled after deployment Auto-healing enables + Alert to DevOps
IBM MQ Queue Manager Queue depth warning threshold Email alert (no auto-healing)
File System File Folder No files received in 30 minutes Alert + Create ticket in ServiceNow

FAQ

How long are Monitoring Events stored?

Event retention is controlled by the DaysToKeepMonitorEvents System Parameter, stored in the Configuration Database. The default is 32 days on a new installation (an update keeps the existing value), and you can extend it based on compliance requirements. The Monitoring Service purges older events every hour.

Do all Monitoring Events trigger alerts?

No. By default an Alarm Plugin entry on a Monitor View alerts only when the Monitor View's own state changes; an entry can instead trigger on each Resource state change. Alerts are only triggered for changes that match configured alert rules (typically Warning, Error, Unavailable, or Connection Error states). Transitions to OK may generate recovery notifications if configured. Some Monitor View membership-only changes, such as removals or re-entry through filter changes, may also stay silent unless a real Resource state change happens at the same time.

Can I search historical Monitoring Events?

Yes! Open a Resource's Resource History (Resource State History) and pick a time span of up to 12 months. To query events across Resources, use the Web API.

What's the difference between a Monitoring Event and a Log Message?

Both are stored in Log Databases, but serve different purposes: monitoring vs. transaction logging.

How do Monitoring Events enable Auto Healing?

The Monitoring Service evaluates each Monitoring Event against configured Auto Healing rules. When a match is found (e.g., "If Windows Service = Stopped, then Execute Start"), the system automatically executes the configured Remote Action.

Can I export Monitoring Events for external analysis?

Yes! Use the Web API to query historical events and export data for integration with BI tools, SLA reporting systems, or custom dashboards.


Next Steps

Add or manage Resource
Add or manage Monitor View
Manage Monitoring Service
View Resource State History
Configure Auto Healing