- 12 minutes to read

What is a Nodinite Monitor View?

Experience seamless, self-service monitoring and management of your integration landscape with Nodinite Monitor Views. Designed for both business and technical users, Monitor Views empower teams to proactively monitor, receive real-time alerts, and take direct action—without waiting for IT. Streamline operations, reduce downtime, and drive continuous improvement with secure, role-based access and automation.

What sets Nodinite Monitor Views apart:

  • ✅ True self-service - Business users monitor, troubleshoot, and fix issues without IT intervention
  • ✅ Real-time alerts anywhere - Email, webhooks, issue tracking systems, Windows Event Log—deliver notifications where your teams work
  • ✅ Intelligent alert recurrence - State-specific escalation strategies prevent alert fatigue (Error: 15 min, Warning: 1 hr, OK: 4 hrs)
  • ✅ One-click problem resolution - Remote Actions (start/stop services, clear queues) eliminate manual server access
  • ✅ Role-based security - Granular permissions ensure users see only what they need—no more, no less
  • ✅ Context-sensitive knowledge - Instant access to operator instructions, SLA information, and system owner details
  • ✅ Auto-healing automation - Configure automated responses to common issues—let Nodinite fix problems before users notice
  • ✅ End-to-end visibility - Monitor complete integration workflows across on-premise, hybrid, and cloud environments
  • ✅ Built-in analytics - Historical statistics and KPIs validate SLAs and identify improvement opportunities

Info

A Nodinite Monitor View includes selected Resources to monitor, enabling both business and technical end-users to enjoy a self-service, proactive way of working.

Get started now: See the Add or Manage Monitor View user guide.

Using a Monitor View someone shared with you? The end-user guides in Getting Started cover it: Monitor Overview and Working with a Monitor View.

Tip

Business users prefer business context? Use BPM instead! While Monitor Views are perfect for technical teams (operations, support, maintenance), business users can monitor the same Resources through BPM process diagrams that reflect real-world business workflows. Same operational data, two perspectives: technical (Monitor Views) or business (BPM with Services). Both support remote actions and self-service monitoring.

The Complete Monitoring Journey

graph TB subgraph "1. Data Collection" MA[fal:fa-monitor-waveform Monitoring Agents
On-premise, hybrid, cloud] R[fal:fa-lightbulb-on Resources
Services, queues, APIs, databases] MA --> | Monitor | R end subgraph "2. Organization" APP[fal:fa-box-open Applications
Group by business system] CAT[fal:fa-folder Categories
Group by resource type] R --> | Organize via | APP R --> | Organize via | CAT end subgraph "3. Configuration" MV[fal:fa-display Monitor View
Curated resource collection] ROLES[fal:fa-users-class Roles
Security & permissions] ALARM[fal:fa-bell Alarm Plugins
Alert destinations] APP --> | Include in | MV CAT --> | Include in | MV R --> | Include in | MV ROLES --> | Secure | MV ALARM --> | Notify via | MV end subgraph "4. Self-Service Operations" USER[fal:fa-user Business User
Monitor & troubleshoot] ACTIONS[fal:fa-wrench Remote Actions
Start/Stop/Fix] KB[fal:fa-book Knowledge Base
Instructions & SLA] STATS[fal:fa-chart-bar Statistics
KPIs & history] MV --> | Access | USER USER --> | Execute | ACTIONS USER --> | Consult | KB USER --> | Analyze | STATS end style MA fill:#3F827B,color:#fff style MV fill:#2678BD,color:#fff style USER fill:#93d16d,color:#000 style ACTIONS fill:#E47528,color:#fff

The complete monitoring journey—from data collection to business user empowerment. Teal marks data collection (Monitoring Agents), blue the Monitor View an Administrator configures, green the business user it serves, and orange the Remote Actions that user can run.

A Nodinite Monitor View is a curated collection of systems integration workflow Resources managed by an Administrator. The Nodinite Administrator grants Business Users access using Role-based security, ensuring the right people have the right visibility and control. Nodinite offers multiple options for sending alerts, through the built-in Alarm Plugins, including an HTTP Webhook for your own systems. You can delegate control and empower users to perform Remote Actions like start and stop—no more waiting for IT! With Nodinite, you eliminate manual labor for problem detection and response; configure monitored Resources for Auto Healing and let Nodinite automatically resolve issues according to your rules.

To create a true managed service, add Knowledge base Articles to Resources in your Monitor Views. This feature fosters personal independence by providing fast, easy access to valuable information such as operator instructions, Custom Metadata like System Owner and SLA.

Nodinite stores historical information, so you can use the view history feature to get the KPIs you need to validate your SLAs and drive continuous improvement.

Share and delegate Fix it, NOW! Learn from mistakes
Quickly provide self-service access for your business and other stakeholders Responsible users can swiftly manage and resolve problems, reducing downtime Drive continuous improvement using actionable statistics

Key Features

# Feature
Visualize problems
Get those responsible aware of the problem
Fix the problems using Remote Actions
Documented solutions
Learn by mistakes and use the statistics feature to prioritize future work

Visualize Problems

Nodinite displays the evaluated state of Resources using intuitive icons and colors, making it easy to spot issues at a glance.
Monitor View rows for BizTalk Resources in Error, Warning, and OK states with Action buttons
Sample from a Monitor View with Resources in different monitoring states.

How a User works with the live list, filters, and the Health Chart is covered in the end-user Monitor Overview guide.

Directly under the filters in each Monitor View, a live bar chart sums up the status codes of all included Resources.

Monitor View Live Monitor tab with the status-code bar chart under the filters, showing Error (3), Warning (3), and OK (16) of 22 Resources (7.10)
Each colored segment is one state with its count in the legend; the total number of Resources is shown to the right.

You can create any number of Monitor Views, each including Resources from one or more Monitoring Agents, Applications, and Categories—mix and match to fit your integration landscape.

Create end-to-end monitoring and alerts for individual system integration workflows, tailored to the exact dependencies of each solution.

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) roMS --- roMV1 roMV2[fal:fa-display Monitor View: Integration Brokers] ---|"Global Configuration"| roTicket(fal:fa-bug Issue Tracking System plugin) roMS --- roMV2 roMV2 ---|"Global Configuration"| roMail roMV3[fal:fa-display Monitor View: SSIS Integration 'Process Orders'] ---|"Global Configuration"| roEventLog(fal:fa-list Event Log plugin) roMS --- roMV3 end style roMS fill:#E47528,color:#fff style roMV1 fill:#2678BD,color:#fff style roMV2 fill:#2678BD,color:#fff style roMV3 fill:#2678BD,color:#fff style roMail fill:#9E59BB,color:#fff style roTicket fill:#9E59BB,color:#fff style roEventLog fill:#9E59BB,color:#fff

Highly configurable, role-based Monitor Views provide self-service for end-users and customizable options for pushing alerts. Orange is the Monitoring Service, blue the Monitor Views, and purple the Alarm Plugins each view uses.


Get Those Responsible Aware of the Problem

Nodinite leverages Custom Metadata from the Repository Model to attach valuable information to alerts, so recipients instantly understand the severity and recommended actions—no searching required.

When a Resource in a Monitor View changes in a way that matters operationally, Nodinite evaluates the Monitor View and may push alerts by Alarm Plugins. Nodinite ships with various mail and Windows Event Log plugins, and you can extend with your own.

When Alerts Are Sent

Situation What users and administrators should expect
A Resource changes state Alerts can be sent according to the Monitor View configuration and recurrence settings.
A Resource is changed, but stays in the same effective state No alert is sent.
You explicitly add a Resource, or add a new include filter that brings it into the Monitor View The affected Monitor View can alert if the change is operationally relevant.
The overall Monitor View stays in the same state Only resource-level alerts may be sent.
Maintenance Mode or postponed Auto Healing applies Alert delivery can be delayed or suppressed while monitoring continues.
No affected Resource can be included in the alert Nodinite skips the notification instead of sending an empty alert.

A change scoped to one Monitor View does not fan out to unrelated Monitor Views.

Important

Monitor View membership-only changes are not fully symmetrical today. Explicit adds behave better than removals, re-entries caused by exclusion changes, and Resources that start matching an older include filter. These transitions can stay silent unless a real Resource state change happens at the same time.

Note

Nodinite v7 loads only the four built-in Alarm Plugins; it does not load custom or 3rd-party Alarm Plugin DLLs. To reach an issue-tracking or incident management system, use the HTTP Webhook plugin.

Tip

You can customize the display of the output using the Nodinite Stylesheets feature.

Intelligent Alert Recurrence

Traditional monitoring floods teams with thousands of alerts for the same issue. Nodinite takes a smarter approach with state-specific alert recurrence using Time Intervals:

Challenge Traditional Monitoring Nodinite Solution
Alert Fatigue 100+ emails for same error 1 initial alert + periodic reminders
Missed Escalations Critical issues buried in noise Error: 15 min, Warning: 1 hr intervals
Resolution Confirmation No feedback when fixed OK state alerts confirm resolution
Business Alignment One-size-fits-all Different intervals per Monitor View

Configure alert recurrence per monitoring state to ensure persistent problems receive attention without overwhelming your team:

  • ❌ Error state: Resend every 15 minutes (critical escalation)
  • ⚠️ Warning state: Resend every 1 hour (periodic reminder)
  • ✅ OK state: Resend every 4 hours (resolution confirmation)
  • 🚫 Unavailable state: Resend every 30 minutes (connectivity issues)
  • Connection Error state: Resend every 15 minutes (critical failures)

Example: A Payment Gateway Outage

A production payment gateway fails at 10:00 AM. With 15-minute recurrence configured:

  1. 10:00 AM - Initial alert: "CRITICAL: Payment Gateway Down"
  2. 10:15 AM - Recurring alert: "REMINDER (15 min): Payment Gateway Still Down"
  3. 10:30 AM - Recurring alert: "REMINDER (30 min): Payment Gateway Still Down"
  4. 10:35 AM - Resolution alert: "RESOLVED: Payment Gateway Online"
  5. 2:35 PM - Confirmation alert: "CONFIRMED OK: Payment Gateway Stable for 4 Hours"

Result: 5 targeted alerts instead of 35+ from traditional monitoring—no alert fatigue, clear escalation path, confirmed resolution.

Learn how to configure alert recurrence →
What is a Time Interval? →

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 style roMS fill:#E47528,color:#fff style roMail fill:#9E59BB,color:#fff style roTicket fill:#9E59BB,color:#fff style roEventLog fill:#9E59BB,color:#fff

From the configuration of Monitor Views, the Monitoring Service (orange) ensures you are always aware by pushing alerts to the recipients (purple)—Nodinite is Always Aware.

Read more about this feature in the 'Alarm Plugins' user guide


History of Distributed Notifications (Alert History)

Distributed Notifications (Alerts) are tracked and stored by Nodinite, providing a searchable history for auditing and troubleshooting. Users can easily search notifications by timespan, and the distributed notifications tab is visible to administrators with External notifications enabled.

Distributed notifications tab with sent and failed alerts per Alarm Plugin in a Monitor View
Example of the 'Distributed Notifications' tab showing a history of sent alerts.

If the system cannot send an alert, it adds the entry to the Alarm Queue for retrying later. Read more in the 'What is an Alarm Queue Entry' user guide.

Missing entries in the Distributed Notifications history?

If you expect an alert in the Distributed Notifications history but cannot find it, check these places in order:

  1. Alarm Queue – An alert that could not be delivered (for example, the mail server or webhook endpoint was unreachable, or the Alarm Plugin is misconfigured) waits here while the Monitoring Service retries it. Open the entry to see the output from the last send attempt. Read more in the 'What is an Alarm Queue Entry' user guide.
  2. Log Audit Search – If the entry is no longer in the Alarm Queue, an administrator may have removed it or purged the queue. These operations are audited; search the Log Audits to find out who did it and when.

Tip

Also verify that the Monitor View has an Alarm Plugin bound and that the alert falls within its configured Time Intervals; otherwise, no alert is sent.


Fix Problems Using Remote Actions

Monitor Views where the Role has the Execute Action permission (Permission Set for Monitor Views) allow end-users to perform Remote Actions like start/stop directly from the interface. Each Resource provides its own set of actions. Nodinite continually adds new functions to streamline daily operations, proving that nothing is impossible.

Empower your power users: they do NOT need to be local administrators or have excessive access rights. Nodinite eliminates the need for RDP, VPNs, and third-party tools—just use your client browser.
Resource Action menu with Control Center Start, Stop, Restart, Details, and Edit Remote Actions
Example of available Remote Actions.

With Nodinite version 6 and later, you can perform the same action on multiple resources simultaneously. Select any number of Resources and use the With selected button to choose the operation and resources to invoke. The end-user steps are in Remote Actions.
With Selected menu offering Exclude and Windows Service Start, Stop, and Restart for two Resources
Example of the With selected button to perform actions on multiple Resources.

Tip

You can also Exclude multiple Resources from the Monitor View using this button.


Documented Solutions

With just one click, you get instant access to operator instructions and documentation (Repository Model). No need for a separate WIKI or time-consuming searches—Nodinite delivers the right information, right when you need it.

You can bind a Monitor View to one or more Integrations and see the benefits immediately:
Monitor View Repository Model tab with an Integration and its Custom Metadata
Example: Access from a Monitor View to your Repository Model.

Add any number of Knowledge base Articles to Resources within the Monitor View for comprehensive, context-sensitive help.
Monitor View rows with Article count badges next to the Action buttons
Access your knowledgebase articles directly from Resources.

Example of Knowledgebase Articles:
Knowledge base Article content editor with formatting toolbar and sample text
WYSIWYG Editor makes it easy to write stylish instructions.

Instant access to information and a WYSIWYG editing experience enable active, living documentation—driving prosperity for Managed Services by Partners.

Read more about this feature in the 'Knowledgebase Articles' user guide


Learn from Mistakes and Use the Statistics Feature to Prioritize Future Work

Many Resources provide statistics, such as CPU usage, web service response time, and BizTalk suspended messages. Nodinite also tracks the history of Monitoring Events. A Monitoring Event is any occasion a Resource changes its evaluated state (e.g., from 'OK' to 'Error'). Administrators can set Expected State to override the state reported by Monitoring Agents, providing flexibility for business needs.

Nodinite gives you statistics on how often problems occur and, crucially, how long it takes to resolve them. This information is displayed directly in Monitor Views. Historical events bar chart with the number of Monitor Events per month
Number of Monitoring Events per month, shown directly in the Monitor View.

With the View History permission (Permission Set for Monitor Views), users can filter and search historical monitor events. Show historical events tab with time span, Log Text, and Status Code filters and state-colored events
Example of historical Monitoring Events for a Resource.

Read more about this feature in the 'Resource State History' user guide


Manage Monitor Views

A Nodinite Administrator can manage a Monitor View by:

See the Monitor Views Overview user guide for a complete list of manageable Monitor Views.


Next Steps

Understanding Monitor Views

For Business Users (Getting Started)

Alert Configuration

Business Process Monitoring

  • BPM - Monitor in business context instead of technical views
  • Services - Bridge between Resources and BPM process steps
  • Repository Model - Documentation and business process visualization

Administration