- 8 minutes to read

Add or Manage Monitor Views

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

Tip

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


Add a New Monitor View

Click the Add/New button to create a new Monitor View, or use Duplicate to clone an existing view.

Add new Monitor View Button
Example of adding a new Monitor View.


Name the Monitor View

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

Add or manage Monitor View
Use clear, descriptive names

Mandatory Fields

Field Required Purpose
Name Yes Unique, user-friendly identifier

Optional Fields

Field Purpose
Description Explain the purpose and scope
Web Site Link to documentation or runbook

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

Assign Roles

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

Assign Roles
Add or remove Roles for the Monitor View

You can select from existing Roles or create new ones.

Assign Roles for Monitor Views
Example of assigning Roles to a Monitor View.

You can also select which access rights each Role has for the Monitor View.

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

Note

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


Assign Access Rights

Set access rights for each Role:

Permission Level Behavior Use Case
Inherited Default, disabled Let role inherit from global settings
Allow Enabled and visible Grant specific access to feature
Block Disabled and blocked Always deny (overrides Allow)

Access options
Example with the set of different permit options.

Features You Can Control

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

Configure Alerts

Select one or more Alarm Plugins to push alerts.

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

Out-of-the-Box Plugins

Email Notifications

Integrations

Select Alarm Plugin
Add or remove Alarm Plugins for Monitor View.

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

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.

Enable Recurrence Settings
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:

State Configuration
OK Time Interval Select the Time Interval to use for resending alarms in the OK state
Warning Time Interval Select the Time Interval to use for resending alarms in the Warning state
Error Time Interval Select the Time Interval to use for resending alarms in the Error state
Unavailable Time Interval Select the Time Interval to use for resending alarms in the Unavailable state
Connection Error Time Interval Select the Time Interval to use for resending alarms in the Connection Error 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
Priority Interval Rationale
Error Every 15 minutes Critical - immediate escalation
Warning Every 1 hour Important - periodic reminder
OK Every 4 hours Confirmation - reassurance

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.


Customize Columns

Choose from:

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

Customize Columns
Customize Columns for Monitor Views option.

Use the Customize Columns dialog to add, remove, or reorder columns. You can also rename columns.
Customize Columns Configuration
Example of the Customize Columns configuration dialog.


Select All Resources from Monitoring Agent

Add, remove, or filter Monitoring Agents to include their Resources.
Sources Option
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.
Filter on Monitoring Agent
Select Monitoring Agents to include monitoring Resources from.


Select All Resources for Category

Select one or more Categories to include their resources.
Filter on Category
Select Categories to include monitoring Resources from.


Select All Resources for Application

Select one or more Applications to include their Resources.
Filter on Application
Select Applications to include monitoring Resources from.


Select Specific Resources

Add, remove, or filter Resources by Monitoring Agent, Application, Category, or name.
Monitoring Resources
Example of selecting specific Resources for the Monitor View.


Exclude Specific Resources

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


Add Repository Model Documentation

Click Edit to add, filter, or remove Integrations. Use the All and Selected tabs to manage your choices.
Manage Integrations
Example of included Integrations on Monitor View

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

Manage Specific Integrations

Note

Manage permissions for viewing the Repository Model as needed.


Save

Click Save or Save and Close to persist your changes.
Save
Make your changes permanent by clicking either Save or Save and close


Using the Monitor View

Click the Show button to open the Monitor View.
Show Monitor View
Example of the Show Monitor View button


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!

Core Monitoring

Security & Access

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

Configuration & Customization

Data Management