Manage Nodinite Monitoring Resources
Understanding Resource Management
Monitoring Resources in Nodinite represent individual components being monitored—such as SQL Server jobs, Windows services, message queues, or file system paths. These Resources populate automatically from Nodinite Monitoring Agents and synchronize their state based on agent-defined polling intervals.
While Resources are automatically discovered and monitored, administrators can customize how state changes are evaluated and how the system responds to issues. The Resource management interface provides both read-only reference information (current state, relationships) and configurable settings (expected state overrides, autohealing actions, external documentation links).
Key capabilities:
- Override state evaluation - Suppress warnings for planned maintenance or known non-issues
- Automate remediation - Configure autohealing rules to restart services or execute scripts when issues occur
- Link to documentation - Provide runbook URLs for operational guidance
- Track state history - Audit all state changes for compliance and troubleshooting
The Resource management interface organizes information into tabs and information panels, separating read-only context from configurable settings.
Managing a Nodinite Monitoring Resource. The interface shows the current state, configuration options, and contextual information about related entities.
Resource Information
The following sections display read-only contextual information about the Resource and its relationships within the Nodinite environment.
General Tab
The General tab displays the current operational state and identification details of the Resource:
- State - Current state of the Resource
- Name - Name of the Resource
- Description - User-friendly description
- Log Text - Log Text is the user-friendly representation of the current monitoring state
- Error Code - Error Code representing current monitoring state (default if not set = 0)
Monitoring Agent
The Resource is discovered and monitored by a specific Monitoring Agent. This panel shows which agent is responsible for polling this Resource and synchronizing its state.
The Monitoring Agent responsible for this Resource.
Application
When a Resource is associated with an Application, this panel displays the business system or integration platform it belongs to. Applications provide logical grouping for operational and organizational purposes.
The Application this Resource belongs to, if applicable.
Category
Resources are organized by Category (such as "Database", "File System", "Message Queue") to help administrators quickly identify resource types across the monitoring landscape.
The Category classification for this Resource.
Monitor Views
This panel lists all Monitor Views that include the current Resource, allowing administrators to see which operational dashboards display this Resource's status.
Monitor Views where this Resource appears.
Configuration
The following settings allow Nodinite Administrators to customize Resource behavior, override state evaluation, and configure automated responses to state changes.
Configuration Tab
The Configuration tab provides three key customization options for administrative control.
The Nodinite Administrator can modify the following properties:
- External Documentation Link - Add external documentation or runbook URLs
- Expected state Configuration - Override state evaluation for planned maintenance
- Autohealing Configuration - Automate remediation actions
Link
You can provide a link to an external Web Site with additional information. When set, the Resource presents inside Monitor Views with an external link icon. The end-user can click on this link to open a new tab with the target URL (Web Site).
Example with an example of the link feature.
Expected state Configuration
The Nodinite Administrator can override the evaluation of the current Monitoring state of the Resource configuring the Expected State feature.
For example, The SQL Monitoring Agent returns a SQL Job that is currently disabled. By design renders a Warning. By setting the Expected State for Warning to OK the alert is suppressed and displayed as being OK. In addition, a small coloured circle shows what's going on. The latter indicates "We hear you - but hey, there's something strange going on here".
Here's an example of a Resource using the Expected State feature.
To manage the Resource, click on the Configuration tab. Then, use the Expected state configuration section to set the expected state according to your preference.
Configure the Expected State to override default state evaluation logic. Add a description to document why you've overridden the monitoring evaluation.
Description Field
For each expected state override, you can add a Description to explain why the monitoring evaluation was superseded. This helps team members understand the reasoning behind the configuration:
- Planned maintenance - "App Pool stopped for weekend patching every Saturday 2-6 AM"
- Known issues - "Warning expected until database upgrade completes Q2 2026"
- Business requirements - "Service runs business hours only (Mon-Fri 8 AM - 6 PM)"
- Temporary overrides - "Suppressed during migration period, remove after go-live"
Adding descriptions improves operational transparency and helps prevent accidental removal of intentional configuration overrides.
Autohealing Configuration
The Nodinite Administrator can add logic to have the system automatically perform an Remote Action depending on the evaluated state.
Click the Edit button to manage the Autohealing configuration.
To manage the Autohealing configuration, click on the Edit button.
From within the Autohealing configuration modal, add one or more Remote Actions to be performed according to the evaluated state.
Here's an example of the Autohealing configuration modal.
Parameter Explanations
- Enabled - When checked, this autohealing entry is active, otherwise it is not
- State - Select the evaluated Monitoring state when to perform the Remote Action
- Action - Select a Remote Action to perform when the Resource is in the specified evaluated Monitoring state
- Attempts - Specify the number of attempts to perform
- Interval - Specify the period in seconds between the retry operations
Custom Metadata
Custom Metadata can be attached directly to any Nodinite Monitoring Resource. This embeds business context—ownership, SLA, emergency contacts, compliance tags, runbook links—into the same entity that drives your monitoring alerts.
Why this matters: When a Resource changes state and triggers an alert, the recipient sees who owns it, what the SLA is, and how to escalate—without any manual lookup. See Alert Enrichment for the full picture.
Typical metadata for Resources:
- Owner - Person or team responsible for the monitored component
- Emergency Contact - Phone number or escalation path for critical failures
- SLA Level - Gold / Silver / Bronze to drive alert prioritization
- Business Impact - Description of what breaks for the business if this Resource fails
- Runbook URL - Link to recovery procedure directly from the monitoring alert
- Compliance Tags - Flag Resources handling GDPR, HIPAA, PCI DSS data
To manage Custom Metadata for a Resource, open the Resource and navigate to the Custom Metadata tab.
Mandatory Fields
Using Mandatory Fields, administrators can enforce that critical Resources always have an Owner and Emergency Contact defined before operational use. This prevents accountability gaps at 3 AM when incidents occur.
Metadata in Alerts
Custom Metadata attached to a Resource flows automatically into Email alerts and HTTP Webhook payloads. Operations teams receive enriched notifications that include owner contact information, SLA level, and runbook links—enabling faster incident response without switching tools.
Learn more: Custom Metadata in Alerts – How metadata appears in Email and HTTP Webhook alerts with real-world before/after examples.
State Change History
History Tab
All state changes for Nodinite Monitoring Resources are persisted as log entries in the Nodinite Log Databases, providing a complete audit trail for compliance and troubleshooting.
Historical state changes for the Resource shown in the History tab. Use this to analyze state patterns, identify recurring issues, or provide evidence for compliance audits.
To alter the number of days to keep the history for Monitoring state changes, please review the DaysToKeepMonitorEvents system parameter user guide.
Business Process Integration
BPM Integration
Resources connected to Services appear in Business Process Models (BPM) for end-to-end business visibility.
When you tie a Resource to a Service in the Repository Model, that Service can be placed in BPM process steps. This creates a powerful bidirectional connection:
From Monitor View to BPM
- View which BPM processes include this Resource
- Understand the business context for operational monitoring
- See how this Resource fits into end-to-end workflows
From BPM to Monitor View
- Click BPM steps to view underlying Resources
- Execute Remote Actions directly from business process diagrams
- See real-time operational status in business context
Benefits for Business Users
- ✅ Monitor business processes without understanding technical details
- ✅ Execute remote actions (start/stop) from BPM views
- ✅ Trace transactions end-to-end across systems
- ✅ Troubleshoot issues in business terms, not just technical logs
Tip
Next Step
Resources Overview
Add or manage Monitor View
Custom Metadata - Enrich Resources with owner, SLA, and emergency contact
Alert Enrichment - See how metadata appears in alerts
Services - Connect Resources to BPM
BPM - See Resources in business process context
Related Topics
Resource Management
- Resources - Understanding Resources
- Resources Overview - Manage all Resources
- Remote Actions - Start/Stop/Restart Resources
- Autohealing - Automated problem resolution (see Configuration tab above)
Organization
- Applications - Group by business system
- Categories - Group by resource type
- Monitoring Agents - Discover Resources
Views & Access
- Monitor Views - Operations perspective
- BPM - Business perspective
- Services - Bridge between Resources and BPM
- Repository Model - Complete documentation
Custom Metadata
- Custom Metadata - Embed owner, SLA, compliance tags, and emergency contacts
- Alert Enrichment - Custom Metadata in Email and HTTP Webhook alerts
- Mandatory Fields - Enforce required metadata on Resources
- Entity Coverage - All entities where Custom Metadata applies
System
- Log Databases - Historical state data
- Monitoring Service - Tracks changes
- Administration - Administrative overview