- 3 minutes to read

What is the Nodinite Monitoring Service?

The Nodinite Monitoring Service delivers proactive, end-to-end monitoring and alerting for your integration landscape. This service ensures you stay informed about system health, resource status, and critical events—empowering you to act before issues impact your business.

✅ Real-time alerts and notifications with flexible alarm plugins
✅ Self-service configuration with role-based Monitor Views
✅ Seamless integration with distributed Monitoring Agents and Auto Healing

The Nodinite Monitoring Service ensures you are always aware of your system's health, based on your custom alerts configuration. This configuration is managed through self-service enabled Monitor Views.

The Monitoring Service is a Windows Service installed as part of the Core Services package. See Prerequisites for installation details. The status of Resources monitored by Monitoring Agents is periodically synchronized by the Monitoring Service.

Features

Operations performed by the Monitoring Service or commands issued by a user come from the following configurations and functionality:

Pushing Alerts

Whenever the evaluation of the state of Resources from any of the Monitoring Agents matches your configuration for Monitor Views.
Alerts are pushed by Alarm Plugins and Nodinite ships with various mail and Windows Event Log plugins.

graph LR subgraph "App Server" roMS(fal:fa-watch-fitness Monitoring Service) end subgraph "Alert recipients" roMS .-> | Send Alert | roMail(fal:fa-envelope Mail) roMS .-> | Send Alert | roTicket(fal:fa-bug Issue Tracking Systems) roMS .-> | Send Alert | roEventLog(fal:fa-list Event Log) end

The Monitoring Service is responsible for making you aware—Nodinite is Always Aware.

Provide Self Service configurations using Monitor Views

The Monitoring Service determines who to notify and how, based on Alarm Plugins configured globally or customized with one or more Monitor Views. With role-based Monitor Views, you can push alerts for a single Resource or combine Resources from different Monitoring Agents to create end-to-end monitoring and alerts for individual system integration workflows, tailored to your solution's dependencies.

graph LR subgraph "App Server" roMS(fal:fa-watch-fitness Monitoring Service) end subgraph "Monitor View Configurations" roMV1[fal:fa-display Monitor View: Queues] ---|Custom Configuration | roMail(fal:fa-envelope e-mail plugin) roMV2[fal:fa-display Monitor View: Integration Brokers] --- | Global Configuration| roTicket(fal:fa-bug Issue Tracking System plugin) roMS --- roMV1 roMS --- roMV2 roMV2 ---| Custom Configuration| roMail roMV3[fal:fa-display Monitor View: SSIS Integration 'Process Orders'] --- | Global Configuration| roEventLog(fal:fa-list Event Log plugin) roMS --- roMV3 end

Highly configurable, role-based Monitor Views provide self-service for end-users and customizable options for pushing alerts.


Periodic Synchronization

The Monitoring Service performs periodic synchronization with the Monitoring Agents. Different Monitoring Agents can have individual synchronization settings, configured via a Monitoring Agent Configuration.

graph LR subgraph "Host with Monitoring Agents" roMonitorAgent(fal:fa-monitor-waveform Monitoring Agent) ro(fal:fa-lightbulb-on Resources to Monitor) roMonitorAgent --> ro end subgraph "Windows Server" roMonitoringService(fal:fa-watch-fitness Monitoring Service) roMonitoringService --> |Monitoring Agent Configuration | roMonitorAgent end

Generic illustration for any type of resource being monitored by a product/service-specific Monitoring Agent.

Synchronization with Monitoring Agents wherever they are

The Monitoring Agents can be installed on-premise or anywhere else. The Monitoring Service can communicate with the Monitoring Agents using any of the following options:


Frequently asked questions

Find solutions to common problems and answers to the Nodinite Monitoring Service FAQ in the Troubleshooting user guide.

How does the Monitoring Service know what to monitor?

A Nodinite Administrator configures both internal and self-service settings:

How does the Monitoring Service know about the evaluated state of a Resource?

A Nodinite Administrator configures the Resources:

  • Knows about the evaluated state from the configuration of Resources
  • Knows about Auto Healing operations to perform from the configuration of Resources

How does the Monitoring Service know how to push alerts?

A Nodinite Administrator configures the Monitor Views:

  • Knows who to send to and with options from the use of Alarm Plugins configured either globally or customized using one or more Monitor Views

Next Step

Add or manage Monitoring Agent
Add or manage Monitor View
Manage Alarm Plugins

Monitor Views Overview
Monitoring Agents
Web Client