- 15 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

You can create a new Monitor View from scratch or duplicate an existing one. In the Administration sidebar, open the Monitor Views Overview and click Add Monitor View, or use Duplicate in the Action menu to clone an existing view.

Monitor Views administration page with the Add Monitor View button highlighted
Administrator interface showing the "Add" button to create a new Monitor View from the Monitor Views management page.

There are four tabs to configure:

  1. General tab - Name, description, Tags, and role assignments
  2. Resources tab - Select which Resources to include (or exclude) in this view using filters or specific selection
  3. External Notifications tab - Configure which Alarm Plugins to use for alerts from this view
  4. Customize Columns tab - Choose which columns to display and their order, or use an existing Display Field Configuration

General tab

💡Essential information

Enter a unique user-friendly name. Then; Optionally, add a Description, Web Site link for related documentation and associate one or more Tags.

Add Monitor View General tab with Name, Description, Web Site, Tags, Roles, and Integrations (7.5.6)
General tab showing the Monitor View name field, description, website link, and tags configuration options. The Roles and Integrations panels sit on the right.

Mandatory Fields

Field Purpose
Name Unique, user-friendly identifier

Optional Fields

Field Purpose
Description Explain the purpose and scope
Web Site Link to documentation or runbook
Tags Add keywords for searchability

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
  • Add Tags to categorize views by team, application, or criticality for easier searching and filtering

Assign Roles

Note

Nodinite Administrators can create and manage Monitor Views, but they do not automatically have access to all views. You must assign them to the appropriate Roles to grant access.

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

Roles panel on the Monitor View General tab with the Edit button
Edit dialog for managing which Roles have access to this Monitor View.

You can select from existing Roles or create new ones.

Assign Roles to Monitor View dialog with the All tab listing Roles to select
Interface for selecting multiple Roles and assigning them access permissions to the Monitor View.

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

Selected tab of the Assign Roles dialog with Access this View, Execute Action, View Metrics, View History, View Repository, and View Articles per Role
Permission matrix showing options to set each Role's access level (Inherited, Allow, or Deny) for specific features like Execute Remote Actions, View Metrics, and View Repository Model.

Tip

When you create a new Monitor View, the Roles listed in the DefaultRolesInViews system parameter are pre-selected. You can remove them or add others before saving, and you can customize the parameter to fit your organizational needs.

Features You Can Control

Tip

  • Use Inherited where possible for easier management
  • Deny always takes precedence if a user is in multiple Roles
  • Grant Remote Actions only to trusted operational teams
  • Deny Access Monitor for a Role in the Permission Set for Monitor Views to block that Role from all Monitor Views

Assign Access Rights

Set access rights for each Role. Each permission is explained in the Permission Set for Monitor Views:

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

Set permit dropdown with Allow, Deny, and Inherited options
Example with the set of different permit options.

Integrations

💡 Link your Monitor View to the Repository Model for instant access to integration context, documentation, and rich alert data.

To access the Repository Model documentation for resources in this Monitor View, you must link the appropriate Integrations. This enriches Monitor Views with architectural context and enables powerful automation capabilities.

graph TD A["fa:fa-display Monitor View with Linked Integrations"] --> B["fa:fa-star Benefits"] B --> C["Access Repository Model Details"] B --> D["Rich Alert Context"] B --> E["Automated Troubleshooting"] B --> F["Instant Escalation Path"] C --> C1["View service dependencies
endpoints, message flows"] D --> D1["Webhook alerts include
full integration architecture"] E --> E1["Auto-create tickets with
business context"] F --> F1["Teams/Slack alerts show
owner and escalation contacts"] style A fill:#2678BD,color:#fff style B fill:#E47528,color:#fff style C fill:#3F827B,color:#fff style D fill:#3F827B,color:#fff style E fill:#3F827B,color:#fff style F fill:#3F827B,color:#fff

Benefits of linking Integrations to your Monitor View - providing architectural context, enriched alerts, automation, and faster troubleshooting. Blue is the Monitor View, orange groups the benefits, and teal shows each benefit.

Click Edit button to add, filter, or remove Integrations. Use the All and Selected tabs to manage your choices.
Monitor View General tab with the Integrations panel highlighted, showing one linked Integration with its Artifact Renaming and description (7.10)
The Integrations panel counts the linked Integrations; Edit opens the selection dialog and the minus icon unlinks one.

Integrations bound to Monitor View dialog with All and Selected tabs
Selected integrations for the Monitor View displayed in a list with the ability to filter and customize.

How It Works

When you link Integrations to your Monitor View:

  • Alerts include full context (Alert Enrichment) – When a resource fails, Alarm Plugins send complete integration architecture details to Teams, Slack, or ServiceNow
  • Self-service troubleshooting – Users can click links in alerts to jump directly to the Repository Model documentation
  • Automation-ready – Use Webhook Alarm Plugins to extract integration details and create incidents with business context
  • Team collaboration – Owner and escalation contact information from the Repository Model is included in alert messages

Note

Manage permissions for viewing the Repository Model as needed. Users need the View Repository permission (Permission Set for Monitor Views) and access to the Repository Model to see linked integration details.

Resources tab

💡Manage Resources to include (or exclude) in the Monitor View

The Nodinite Administrator can select which Resources to include in the Monitor View. The filtering feature makes use of one or more include or exclude filters to determine which Resources are included in the view. You can include all resources from specific Monitoring Agents, filter by Application or Category (maintained in the Applications Overview and Categories Overview), or select specific resources. You can also exclude specific resources after including them. The layout and filtering options give you maximum flexibility to create views that match your operational needs. This feature has changed significantly in recent versions to provide more intuitive and powerful resource selection.

In the 'Resources included in Monitor View' panel; Click the Edit button to manage which Resources are included in this Monitor View.

Note

There is a checkbox on each filter entry to include or exclude that filter. This allows you to create complex combinations of included and excluded resources. For example, you could include all resources from a specific Monitoring Agent but then exclude certain critical resources for a more focused view. Include filters have an 'OR' relationship, while exclude filters have an 'AND' and 'NOT' relationship, giving you powerful control over the final set of resources in the view.

Assign Resources to Monitor View dialog with an include filter by Monitoring Agent, Category, Application, and Resource Name
Resource selection dialog showing filtering options by Monitoring Agents, Categories, Applications, and Resources with include/exclude checkboxes.

Input field Purpose Note Single Selection Multi Selection using a filter
Monitoring Agents Select one or more Monitoring Agents to include all their Resources This is a broad filter that includes everything from the selected agents ✅ Yes ❌ No
Categories Select one or more Categories to include their resources This allows you to include resources based on their functional grouping ✅ Yes ❌ No
Applications Select one (single selection mode) or more Applications (By name mode) to include their resources This allows you to include resources based on the application they belong to ✅ Yes ✅ Yes (By Name mode, a filter is required)
Resource Name Search and select specific Resources by name This is a precise filter for including specific resources by filter ❌ No ✅ Yes (a filter is required)

Filter Logic

Resource name filters support SQL LIKE pattern syntax. Review the Microsoft SQL documentation for complete details.

Wildcard Description Example
% Any string of zero or more characters %computer% matches any name containing "computer"
_ (underscore) Any single character _ean matches "Dean", "Sean", "Jean" (4 letters ending in "ean")
[a-f] or [abc] Any single character within the specified range or set [C-P]arsen matches "Carsen", "Larsen", "Marsen" (starting with C through P)
[^a-f] or [^abc] Any single character NOT within the specified range or set de[^l]% matches "design", "desync" but NOT "dell" or "delete"

Pattern Examples

  • Order% – Matches "Order", "OrderReceiver", "OrderProcessing"
  • %_Error – Matches any name that ends with "Error" and has at least one character before it (like "ZError", "QueueError")
  • [A-Z][0-9]% – Matches names that start with a letter followed by a digit (like "A1Orders")
  • Service[^_] – Matches "ServiceA", "ServiceX" but NOT "Service_" patterns

Click on the filter to see a preview of which resources will be included in the view based on that filter. This allows you to validate your filter criteria before saving the view.

Resource filter preview pane before a filter is modified or clicked
Filter preview pane showing no results when no filter criteria are entered or no Resources match the current selection.

If you have a large number of resources that match the filter criteria, the preview will show a capped list with a message indicating that not all resources are shown. This helps you understand the scope of your filter without overwhelming you with too much information in the preview. Resource filter preview capped at the first matches of 810 Resources found
Filter preview showing a sample of matching Resources (capped at maximum display) with message indicating total count exceeds preview limit.

Tip

Include or Exclude? Click the checkbox next to each filter entry to use that filter as either include or exclude.

Add Filter

Click the Add Filter button to create a new filter entry. You may need to toggle the checkbox to include or exclude the filter after adding it. Add Filter button in the Assign Resources dialog
"Add Filter" button interface for creating a new resource filter entry with options to include or exclude specific Monitoring Agents, Categories, Applications, or Resources.

Add Specific Resources

If you want to include (or exclude) specific Resources without using the broader filters, you can use the Add Specific option. This allows you to search for and select individual resources to include in the view. You can also use this option to exclude specific resources after including them with broader filters. Add Specific button in the Assign Resources dialog
Search interface for finding and selecting individual Resources to include or exclude, useful when you need fine-grained control over resource selection.

You may need to toggle the checkbox to include or exclude the filter after adding it.

External Notifications tab

💡Configure alerts to tell the world when there's a change and need to know

Select one or more Alarm Plugin entries to push alerts outside Nodinite. Since 7.2.0, a Monitor View holds no alarm settings; the selected entries hold them (Add or manage Alarm Plugin).

Monitor View External notifications tab with the Alarm Plugins panel listing the selected Email options entry (7.10)
Click Edit in the Alarm Plugins panel to add or remove entries; the minus icon removes one.

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 System) 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

The Monitoring Service (orange) pushes alerts from the Monitor View to the recipients of each selected Alarm Plugin (purple).

Out-of-the-Box Plugins

Assign Alarm Plugins to Monitor View dialog with the four default entries and the Email options entries created by the migration (7.10)
The Assign Alarm Plugins to Monitor View dialog lists every Alarm Plugin entry: the four defaults (Email, Email options, Event Log, Webhook) and the entries the 7.2.0 migration created per Monitor View. Check the entries to use and click Confirm and close.

Recurrence and the alert layout (Stylesheets) are set on the entry. For different settings, select another entry.

Note

The Nodinite 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 now 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 on an Alarm Plugin entry, Nodinite resends alerts at regular intervals for ongoing issues. This ensures persistent problems don't go unnoticed.

Enable Recurrence

Check Enable Recurrence on the Recurrence tab of the Alarm Plugin entry (Add or manage Alarm Plugin); it applies to every Monitor View that selects the entry.

Enable Recurrence checkbox with Ok, Warning, Error, Connection Error, and Unavailable Time Interval selectors
Recurrence configuration panel showing interval selection for each monitoring state (OK, Warning, Error, Unavailable, Connection Error) to control alert reminder frequency.

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 → Customize → Time Intervals, see Time Intervals - Overview.

Customize Columns tab

💡Control what information is present and in what order

Choose from:

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

Customize columns tab with the Default option selected and the default columns Status Code, Name, Monitor Agent, Category, Application, and Log Text (7.10)
The tab offers Default, Manual configuration, and Existing configuration (a Display Field Configuration); Default lists the columns Nodinite shows out of the box.

Use the Customize Columns dialog to add, remove, or reorder columns. You can also rename columns.
Customized columns in result dialog with Artifact Renaming and selected Display Fields
Column editor interface with options to add, remove, rename, and reorder columns displayed in the Monitor View.

Save

Click Save or Save and Close to persist your changes.
Save, Save and close, and Cancel buttons in the Monitor View editor
Save buttons for persisting Monitor View configuration changes - "Save" to keep working, "Save and Close" to apply and exit.

Using the Monitor View

Click the Show button to open the Monitor View.
Show button next to Add Monitor View, Duplicate, and Save in the Monitor View editor
"Show" button in the Monitor Views management interface that opens and displays the configured Monitor View for users.

Everything users do in the view (filtering, sorting, Remote Actions, and history) is covered in the end-user guides Monitor Overview and Working with a Monitor View.

Next Steps

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

Configuration & Customization

Data Management