What is the Monitoring Service?

Nodinite Monitoring Service is responsible for making sure you get aware according to your alerts configuration. This configuration comes from the use of self service enabled Monitor Views.

The Monitoring Service is a Windows Service installed as part of the Core Services package, see Prerequisites for installation related information. Status of Resources being monitored by Monitoring Agents are periodically synchronized by the Monitoring Service.

Features

Operations performed by the Monitoring Service or commands issued by an user comes 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

Monitoring Service is responsible for making you aware, Nodinite is Always Aware

Provide Self Service configurations using Monitor Views

The Monitoring Service "knows" who to send to and with what options from the use of Alarm Plugins configured either globally or customized using one or more Monitor Views. Using the concept of Role based Monitor Views means that you can push alerts for anything from 1 single Resource, or you can mix Resources from different Monitoring Agents to create end to end monitoring and alerts for individual system integration workflows with exactly the dependencies that exists for each solution.

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

Highly configurable role based Monitor Views provides self service for end users as well as customizable options for pushing alerts


Periodic Synchronization

The Monitoring Service performs periodic Synchronization with the Monitoring Agents. Different instances of the Monitoring Agents may have individual synchronization settings set by configuring a Monitoring Agent Configuration.

graph LR subgraph "Host with Monitoring Agents" roMonitorAgent(fal:fa-heart-rate 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

Common problems and FAQ for the Monitoring Service not found on this page can be found in the troubleshooting page.

How does the Monitoring Service know what to Monitor?

The Monitoring Service "knows" this because a Nodinite Administrator has configured both internal configurations and configurations for self service

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

The Monitoring Service "knows" this because a Nodinite Administrator has configured the Resources

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

How does the Monitoring Service know how to push alerts?

The Monitoring Service "knows" this because a Nodinite Administrator has configured 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