Add or Manage Monitor Views

Nodinite Monitor Views empower your business with self-service monitoring, advanced alerting, and secure, role-based access. This guide shows you how to create, configure, and manage Monitor Views for maximum operational insight and business agility.

What You'll Learn

Core Features

• Create and duplicate Monitor Views
• Configure role-based access control
• Set up advanced alert notifications
• Customize monitoring columns

Advanced Options

• Fine-tune resource selection
• Configure alert recurrence
• Link Repository Model documentation
• Build custom monitoring dashboards

Step-by-Step: Create and Manage a Monitor View

Follow these steps to create and configure a Monitor View that fits your business needs. Each step includes clear input, action, and result sections for easy reference.

Tip

You can duplicate an existing Monitor View to quickly create variations for different teams or scenarios.

Step 1: Add or Manage a Monitor View

Input:
You want to create a new Monitor View or duplicate an existing one.

Action:
Click the Add/New button to create a new Monitor View, or use Duplicate to clone the current view.

Example of adding a new Monitor View.

Result:
A new Monitor View is created and ready for configuration.

Step 2: Name the Monitor View

Input:
You need to assign a unique, descriptive name to your Monitor View.

Action:
Enter a user-friendly name. Optionally, add a description and a website link for documentation.

Use clear, descriptive names

Result:
The Monitor View is clearly identified for Users.

Configuration Fields:

Tip

• Use business-friendly names: "Production Orders" not "MonView_001"
• Include environment: "Prod - Customer API" vs "Dev - Customer API"
• Add website links to runbooks or dashboards for quick reference

Step 3: Assign Roles

Input:
You want to control who can access the Monitor View.

Action:
Click Edit to add or remove Roles. Only users in assigned Roles can see or use the Monitor View.

Add or remove Roles for the Monitor View

You can select from existing Roles or create new ones.

Example of assigning Roles to a Monitor View.

Furthermore, you can select which access rights each Role has for the Monitor View.

Example of assigning access rights for Roles in a Monitor View.

Result:
Access to the Monitor Viewis restricted to selected Roles.

Note: Nodinite Administrators can create and manage Monitor Views, but only assigned Roles have access to the actual view.

Step 4: Assign Access Rights

Input:
You want to define what each Role can do in the Monitor View.

Action:
Set access rights for each Role. Choose from:

Example with the set of different permit options.

Result:
Each Role has specific permissions for the Monitor View.

Features you can control:

• Access this View
• Execute Remote Actions
• View Metrics
• View History
• View Repository Model
• View Articles

Tip

• Use Inherited where possible for easier management
• Block always takes precedence if a user is in multiple Roles
• Grant Remote Actions only to trusted operational teams

Step 5: Configure Alerts

Input:
You want to notify users about important events in the Monitor View.

Action:
Select one or more Alarm Plugins to push alerts. Out-of-the-box plugins include:

Email Notifications

• E-mail - Simple email alerts
• E-mail with options - Interactive email with actions

Integrations

• Windows Event Log - SCOM integration
• HTTP Webhook - Custom integrations (Slack, Teams, PagerDuty)

Add or remove Alarm Plugins for Monitor View.

You can also configure recurrence for repeated alerts and customize alert content using the Stylesheets feature.

Result:
Users receive timely alerts based on your configuration.

Note

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

How Nodinite's Smart Alert Triggering Works

Nodinite takes a fundamentally different approach to alerting compared to traditional monitoring products. Understanding this philosophy helps you configure alerts effectively and reduces alert fatigue.

The Traditional Problem

Many monitoring products trigger an alert for every single resource state change. In production environments, this can easily produce hundreds of thousands of alerts:

• A dead letter queue with 1 message triggers an alert
• The same queue with 99 messages triggers another alert
• When it reaches 1,001 messages, yet another alert fires

The Nodinite Approach

Nodinite uses Monitor View-level triggering as the intelligent control point:

1. Monitor View State Drives Alerts - If all resources in a Monitor View are OK, the Monitor View state is OK
2. First Problem Triggers Alert - When Nodinite detects the first resource in error state, the Monitor View changes to error and triggers the alert
3. Additional Resources Extend Alert - If another resource also turns into error (or any other state), this triggers a new alert (configurable via recurrence settings)
4. Focus on What Matters - Whether there's 1 dead letter message or 1,001, the fact remains: there's already a problem you should solve

Business Benefits

• Reduced Noise - No alert storms from the same ongoing issue
• Focused Response - Team responds to the problem, not individual state changes
• Intelligent Escalation - Configure recurrence intervals to remind without overwhelming
• Cost Efficiency - Less time filtering false alerts, more time solving real problems

Example Scenario

Without Nodinite (traditional approach):

• 10:00 AM: Alert - Queue has 1 message in error
• 10:05 AM: Alert - Queue has 50 messages in error
• 10:10 AM: Alert - Queue has 200 messages in error
• Result: 3 alerts for the same problem, team wastes time correlating

With Nodinite (intelligent approach):

• 10:00 AM: Alert - Monitor View "Production Orders" changed to Error state
• 10:15 AM: Reminder alert (recurrence configured for every 15 minutes)
• Result: Clear problem identification, team focuses on root cause

This approach keeps the noise down and helps you focus on what's important and what's not.

Configuring Alert Recurrence

When you enable recurrence for an Alarm Plugin, you can configure Nodinite to resend alerts at regular intervals for ongoing issues. This ensures persistent problems don't go unnoticed.

Enable Recurrence

Check the Enable Recurrence checkbox to activate recurring alerts for this Monitor View.

Configure recurrence intervals for each monitoring state.

Configure Time Intervals by State

For each monitoring state, select a Time Interval that defines how often alerts should be resent while the Monitor View remains in that state:

Tip

• Error alerts every 15 minutes - Critical errors need immediate attention
• Warning alerts every 1 hour - Warnings can wait longer between reminders
• OK alerts every 4 hours - Confirmation of resolution sent periodically

This helps prioritize critical issues without overwhelming recipients with notification fatigue.

Example Configuration

Note

You must have Time Intervals configured in Nodinite before you can use them for recurrence. Time Intervals are managed in Administration → Settings → Time Intervals.

Step 6: Customize Columns

Input:
You want to control which columns appear in the Monitor View.

Action:
Choose from:

• Default Columns (provided by Nodinite)
• Use an existing Display Field Configuration
• Advanced: Drag, drop, rename, and add dynamic columns

Customize Columns for Monitor Views option.

Result:
The Monitor Viewdisplays only the columns you need.

You can use the Customize Columns dialog to add, remove, or reorder columns. You can also rename columns.

Example of the Customize Columns configuration dialog.

Step 7: Select All Resources from Monitoring Agent

Input:
You want to include all Resources from specific Monitoring Agents.

Action:
Add, remove, or filter Monitoring Agents to include their Resources.

Select Monitoring Agents to include monitoring Resources from.

You can select one or more Monitoring Agents to include all their Resources in the Monitor View.

Select Monitoring Agents to include monitoring Resources from.

Result:
All Resources from selected Monitoring Agents are included.

Step 8: Select All Resources for Category

Input:
You want to monitor Resources by Category.

Action:
Select one or more Categories to include their resources.

Select Categories to include monitoring Resources from.

Result:
All Resources in selected Categories are included.

Step 9: Select All Resources for Application

Input:
You want to monitor Resources by Application.

Action:
Select one or more Applications to include their Resources.

Select Applications to include monitoring Resources from.

Result:
All Resources in selected Applications are included.

Step 10: Select Specific Resource

Input:
You want to include only specific resources.

Action:
Add, remove, or filter Resources by Monitoring Agent, Application, Category, or name.

Example of selecting specific Resources for the Monitor View.

Result:
Only selectedResources are included in the Monitor View.

Step 11: Exclude Specific Resource

Input:
You want to exclude certain Resources from the Monitor View.

Action:
After choosing a Monitoring Agent, exclude Resources as needed. Filter by Monitoring Agent, Application, Category, or name.

Result:
ExcludedResourcesare not monitored in this view.

Step 12: Add Repository Model Documentation

Input:
You want to link Integrations (Repository Model) to the Monitor View.

Action:
Click Edit to add, filter, or remove Integrations. Use the All and Selected tabs to manage your choices.

Example of included Integrations on Monitor View

You can select specific Integrations to link to the Monitor View.

Result:
Selected Integrations are linked to the Monitor View.

Note: Manage permissions for viewing the Repository Model as needed.

Step 13: Save

Input:
You have finished configuring the Monitor View.

Action:
Click Save or Save and Close to persist your changes.

Make your changes permanent by clicking either Save or Save and close

Result:
Your Monitor Viewis saved and ready for use.

Step 14: Using the Monitor View

Input:
You want to view and use the Monitor View you just configured.

Action:
Click the Show button to open the Monitor View.

Example of the Show Monitor View button

Result:
You can now monitor, alert, and troubleshoot using your custom Monitor View.

Next Step

Tip

Create a Monitor View for dashboard usage. Place a large screen in your support room and use a dedicated Nodinite user. No notifications are sent if no plugins are selected—perfect for silent monitoring displays!

Related Topics

Core Monitoring

• Resource State History - Track resource state changes over time
• Remote Actions - Execute actions from Monitor Views
• Monitoring Service - Core monitoring engine
• Monitoring Agents - Data collection sources

Security & Access

• Users - Manage user accounts
• Roles - Configure role-based access control

Configuration & Customization

• Stylesheets - Customize alert appearance
• Time Interval Configurations - Define recurring intervals
• Display Field Configurations - Column customization
• Alarm Plugins - Configure notification channels

Data Management

• Applications - Group resources by application
• Categories - Organize resources by category
• Resources - Individual monitoring targets
• Integrations - Link to Repository Model
• Articles - Knowledge base integration
• Log Audits - Audit trail for changes
• DaysToKeepMonitorEvents - Data retention policy