Monitor Management Sidebar Menu Item
Unlock the full power of Nodinite Monitor Management—where self-service monitoring meets enterprise-grade automation. This page guides integration experts and customers to navigate, configure, and optimize the Monitor Management sub-menu in the Administration sidebar of the Nodinite Web Client.
With Nodinite Monitor Management, you get:
- ✅ Self-service empowerment - Business users monitor and troubleshoot without IT intervention
- ✅ End-to-end visibility - Monitor every link in your integration chain from on-premise to cloud
- ✅ Proactive automation - Auto Healing with Remote Actions eliminates manual intervention
- ✅ Role-based security - Granular access control through Roles ensures the right people see the right data
- ✅ Instant alerts - Real-time notifications via email, webhooks, or issue tracking systems
- ✅ Built-in knowledge base - Context-sensitive documentation and operator instructions at your fingertips
On this page, a Nodinite Administrator learns how to manage the Monitor Management sub-menu, including Monitor Views, Monitor Agents, Applications, Categories, and Resources. Business users who only use Monitor Views start at the Monitor Overview in Getting Started instead.
The 'Monitor Management' menu item in the sidebar of the Nodinite Web Client—your gateway to unified monitoring.
Sub-menu Items
The following sub-menu items empower you to optimize and secure your monitoring landscape:
- Monitor Views – Manage what to include in the Monitoring, who can see it, and where alerts go.
- Monitor Agents – Register agents, open the Remote Configuration, and access diagnostic files.
- Applications – Group Resources by application for streamlined management.
- Categories – Organize Resources by category for clarity and control.
- Resources – View entries from Monitoring Agents, and set Expected State and Auto Healing.
configured by you) roS(fal:fa-monitor-waveform Monitoring Agents
registered by you) roA(fal:fa-box-open Applications
discovered) roC(fal:fa-folder Categories
discovered) roR(fal:fa-lightbulb-on Resources
discovered) roMV -->|"0..*"| roS roS -->|"0..*"| roR roA -->|"0..*"| roR roC -->|"0..*"| roR roMV -->|"0..*"| roA roMV -->|"0..*"| roC roMV -->|"0..*"| roR end style roMV fill:#2678BD,color:#fff style roS fill:#2678BD,color:#fff style roA fill:#3F827B,color:#fff style roC fill:#3F827B,color:#fff style roR fill:#3F827B,color:#fff
The Monitor Management sub-menu relationships. Blue nodes are entries an Administrator creates (Monitor Views and Monitoring Agent registrations); teal nodes (Applications, Categories, and Resources) are discovered by the Monitoring Agents and synchronized by the Monitoring Service, so you manage their settings but never create them by hand.
How It Works: The Monitoring Flow
Collect data from Resources"] --> MS["fal:fa-watch-fitness Monitoring Service
Evaluates state changes"] MS --> MV["fal:fa-display Monitor Views
Filter and organize Resources"] MS --> AP["fal:fa-bell Alarm Plugins
Send real-time alerts"] MV --> R["fal:fa-users-class Roles
Control access permissions"] R --> U["fal:fa-user Business Users
Self-service monitoring"] U --> RA["fal:fa-wrench Remote Actions
Start/Stop/Fix instantly"] U --> KB["fal:fa-book Knowledge Base
Operator instructions"] style MA fill:#3F827B,color:#fff style MS fill:#E47528,color:#fff style AP fill:#E47528,color:#fff style MV fill:#2678BD,color:#fff style R fill:#2678BD,color:#fff style U fill:#93d16d,color:#000 style RA fill:#93d16d,color:#000 style KB fill:#93d16d,color:#000
From data collection to business user empowerment. Teal is data collection (Monitoring Agents), orange is Core Services processing (Monitoring Service and Alarm Plugins), blue is what an Administrator configures (Monitor Views and Roles), and green is the self-service outcome for business users.
Configure Alerts using one or more Alarm Plugins in Monitor Views with Resources. The Nodinite Monitoring Service pushes the Alerts according to individual Monitor View settings, including recurrence based on Time Intervals. Monitor Views determine what is being monitored, and Resources provide the specific entries from the Monitoring Agents.
The self-service advantage: Business users can view real-time status, receive alerts, execute Remote Actions (start/stop services), and access documentation—all without waiting for IT. This eliminates bottlenecks, reduces downtime, and empowers teams to resolve issues independently.
Administrator Tasks at a Glance
| Task | Where to do it |
|---|---|
| Register a Monitoring Agent installed on a remote server | Add or manage Monitoring Agent |
| Change what an agent monitors (thresholds, connections, Debug flag) | Remote Configuration |
| Let agents explain errors with AI | AI Diagnostics |
| Create a Monitor View, pick Resources, bind Alarm Plugins | Add or manage Monitor View |
| Decide who can see a Monitor View and run Remote Actions | Roles and the Monitor Views permission set |
| Pre-select Roles on new Monitor Views | DefaultRolesInViews System Parameter |
| Override the state an agent reports, or automate fixes | Expected State and Auto Healing |
| Mute alerts during planned work | Maintenance Mode on a User Notification |
| Find alerts that were not delivered | Alarm Queue |
| Keep or purge Resource state history and agent configuration backups | DaysToKeepMonitorEvents and DaysToKeepMonitorAgentBackups |
| Restore a deleted Monitor View or Monitoring Agent | Show deleted records |
| See who changed what | Log Audit Search |
What Business Users Do with Monitor Views
Everything business users do with a Monitor View you share with them is documented in Getting Started, so these Administration pages stay focused on setup:
- Monitor Overview and Working with a Monitor View – Live status, filters, and the Action button
- Remote Actions – Start, stop, and fix Resources without server access
- Resource State History – When problems happened and how long they lasted
- Know when orders stop coming in – A goal-based scenario built on a Monitor View
- Show who to call in alerts – Owner and runbook details in every alert
Sensitive Data Warning for Alerts
Treat all monitoring text fields as potentially alert-visible operational data. This includes Description fields on Resources, Categories, and Applications, plus Custom Metadata values attached to monitored entities.
Warning
Do not store secrets in monitoring descriptions or metadata. Passwords, API keys, tokens, private keys, and full connection strings can be exposed in Email and HTTP Webhook alerts.
What Can Be Exposed
- Description text from monitored entities
- Custom Metadata values used for enrichment
- Context copied into alert templates, tickets, and chat notifications
Safe Data Hygiene Rules
- Store only operational context in descriptions and metadata (owner, SLA, escalation path, runbook URL)
- Keep credentials in approved secret stores, not in Nodinite text fields
- Replace sensitive values with neutral references such as
SecretRef=PaymentDb-Prod - Review alert templates (Stylesheets) and webhook payload mappings before production rollout
For details on how metadata is included in alerts, see Alert Enrichment.
Next Steps
- Add or manage Monitor View
- Add or manage Monitoring Agent
- Add or manage Resource
- Add or manage Categories
- Add or manage Application
Related Topics
Monitor Management Components
Integration with Repository Model
- Services – Link Resources to Services for BPM integration
- BPM – Visualize business processes with operational monitoring
- Repository Model – Document your integration landscape
- Articles – Knowledge base and operator instructions
Alerting and Actions
- Alarm Plugins – Configure alert destinations
- Remote Actions – Self-service problem resolution
- Monitoring Service – Core monitoring engine
- Resource State History – Historical statistics and KPIs
Security and Administration
- Roles – Role-based access control
- Administration
- Web Client