Manage Nodinite Monitoring Resources
Note
Resources are automatically discovered and synchronized by Nodinite Monitoring Agents. Administrators can customize how state changes are evaluated, apply auto-healing rules, and enrich operational context with metadata.
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 user 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)
Sensitive Data Warning
Description and Custom Metadata fields are operational context fields and can appear in alert outputs.
Warning
Do not place secrets in Description or Custom Metadata. Passwords, API keys, tokens, private keys, and full connection strings can be exposed through Email and HTTP Webhook alerts.
Use these fields for non-secret context only, for example owner, SLA, escalation path, and runbook URLs. If you need to reference credentials, store them in an approved secret vault and use a neutral reference value instead.
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 further organized by Category (such as "Azure Function", "Windows Service", "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.
Example of the Monitor Views panel showing all 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 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 (see Expected State)
- Autohealing Configuration - Automate remediation actions (see Auto Healing)
Example of the Configuration tab for a Nodinite Monitoring Resource. This is where administrators can set external links, expected state overrides, and autohealing 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 of a Resource with an external link to a runbook or documentation. The icon appears in Monitor Views for quick access.
Expected state Configuration
Use this section to set an override for how the current state is evaluated for this specific Resource. For conceptual guidance, use cases, and status code reference, see Expected State.
Example of the Expected state configuration area in the Resource editor.
Configure Expected State
Use this section to configure an override for how the current state is evaluated for this specific Resource. For scenarios, governance, and operational guidance, see Expected State.
- Open the Configuration tab for the Resource.
- In Expected state configuration, map the evaluated state to the expected outcome.
- Add a clear Description so operators understand why the override exists.
Example of a Resource showing an Expected State indicator in the monitoring UI.
Autohealing Configuration
Use this section to configure automatic remediation on this specific Resource. For scenarios, governance, and operational guidance, see Auto Healing.
Example of the Autohealing section before any actions are configured.
Configure Autohealing
- Click Edit in the Autohealing section.
- Add one or more Remote Actions for the selected evaluated state.
- Set Attempts and Interval based on your retry policy.
- Enable the entry and save.
Example of the Autohealing configuration modal with state-based actions.
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 panel at the bottom of the General tab.
Example of the Custom Metadata panel for a Nodinite Monitoring Resource. Administrators can add, edit, or remove metadata fields to enrich operational context.
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 the Alarm Plugins such as Email alerts and HTTP Webhook. 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
- Open a BPM with Services to view associated 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