- 5 minutes to read

Monitor View General Tab

The General tab is the first of four tabs when you add or manage a Monitor View. It decides what the Monitor View is called, who can use it and with which rights, and which Integrations give its alerts business context from the Repository Model. Getting the Roles right matters most: a Monitor View is only useful to the people whose Roles are assigned to it, and the access rights decide whether they may also run Remote Actions or read the documentation.

Understanding the General tab

graph LR MV["fa:fa-display Monitor View"] --> ID["fa:fa-tag Name, Description,
Web Site, Tags"] MV --> RO["fa:fa-users-class Roles
access rights per Role"] MV --> IN["fa:fa-puzzle-piece Integrations
Repository Model context"] RO --> US["fa:fa-user Users in those Roles
see and use the view"] IN --> AL["fa:fa-bell Alerts and users
get integration context"] style MV fill:#2678BD,color:#fff style ID fill:#3F827B,color:#fff style RO fill:#E47528,color:#fff style IN fill:#9E59BB,color:#fff

The Monitor View (blue) has identity fields (teal), Roles with access rights that decide who uses it (orange), and linked Integrations that add Repository Model context (purple).

Part Decides Required
Name, Description, Web Site, Tags How users find and recognise the view Name only
Roles Who can open the view, and what they may do in it ✅ Without a Role, nobody sees the view
Integrations Which Repository Model context the view and its alerts carry Optional

Name, Description, Web Site, and Tags

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

Next Steps