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. Either from the Overview page or the Manage Monitor Views page,

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

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
   • Roles panel - Assign which Roles can access this view and their permissions
   • Integrations panel - Link to Repository Model documentation for resources in this view
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.

General tab showing the Monitor View name field, description, website link, and tags configuration options.

Mandatory Fields

Optional 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
• 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.

Edit dialog for managing which Roles have access to this Monitor View.

You can select from existing Roles or create new ones.

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.

Permission matrix showing options to set each Role's access level (Inherited, Allow, or Block) for specific features like Execute Remote Actions, View Metrics, and View Repository Model.

Tip

The default set of Roles available in a Monitor View is determined by the DefaultRolesInViews system parameter. You can customize this list to fit your organizational needs.

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

Assign Access Rights

Set access rights for each Role:

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.

Why Link Integrations?

Benefits of linking Integrations to your Monitor View - providing architectural context, enriched alerts, automation, and faster troubleshooting.

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

Integration selection interface showing all available Integrations with option to select which ones to link to this Monitor View.

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 – 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 must have access to the Repository Model feature 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, 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.

Resource selection dialog showing filtering options by Monitoring Agents, Categories, Applications, and Resources with include/exclude checkboxes.

Filter Logic

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

Pattern examples:

• Order% – Matches "Order", "OrderReceiver", "OrderProcessing"
• %_Error – Matches any name ending with single character + "Error" (like "ZError", "AError")
• [A-Z][0-9]* – Matches names starting with a letter followed by any numbers
• 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.

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.
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 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.
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 Plugins to push alerts outside Nodinite.

Out-of-the-Box Plugins

Email Notifications

• E-mail - Simple email alerts. Not available when Nodinite is configured to use OAuth 2.x.
• E-mail with options - Interactive email with actions
• 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.

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

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:

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.

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

Column customization tab showing options to use default columns, apply a Display Field Configuration, or configure custom columns.

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

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 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 in the Monitor Views management interface that opens and displays the configured Monitor View for users.

Please read the Monitor Overview documentation to learn how users can interact with the Monitor View, including filtering, sorting, executing Remote Actions, and viewing resource details.

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