- 4 minutes to read

What is a Resource?

Monitor every link in your integration chain—from on-premise to cloud—with Nodinite Resources. Each Resource represents a specific, monitorable component in your systems integration landscape, providing real-time health status, automated alerts, and self-service control.

Key benefits:

  • ✅ End-to-end visibility - Every link in your integration chain becomes a monitorable Resource
  • ✅ Real-time health status - Instant visual indicators (OK, Warning, Error, Unavailable, Connection Error)
  • ✅ Self-service operations - Business users can monitor and manage Resources without IT access
  • ✅ Flexible organization - Group Resources by Application or Category for any business scenario
  • ✅ Context-sensitive help - Associate knowledge base articles with Resources for instant troubleshooting guidance

The Resource Journey

graph LR subgraph "Data Source" MA[fal:fa-monitor-waveform Monitoring Agent
Collects health data] end subgraph "Resource Definition" R[fal:fa-lightbulb-on Resource
Queue, Service, API, DB] APP[fal:fa-box-open Application] CAT[fal:fa-folder Category] MA -->|Discovers| R R -->|Belongs to| APP R -->|Classified as| CAT end subgraph "Monitoring" MS[fal:fa-watch-fitness Monitoring Service
Tracks state changes] MV[fal:fa-display Monitor View
Displays to users] R -->|Evaluated by| MS MS -->|Includes in| MV end subgraph "Self-Service" USER[fal:fa-user Business User
Monitor & control] MV -->|Accessible to| USER end style R fill:#fff4e1 style MV fill:#e8f5e9 style USER fill:#f3e5f5

Diagram: From data collection to business user self-service—every Resource flows through Nodinite's monitoring architecture

A Resource is a specific object/unit being monitored by a specific Monitoring Agent. A Resource originates from Monitoring Agents. The current state of the Resource is tracked by the Monitoring Service.

The design goal is to represent every link in the System Integration chain as a Resource—enabling true end-to-end monitoring.

The Bridge Between Monitoring and BPM

Resources are the critical link that connects real-time monitoring with business process visualization:

  • In Monitor Views - Resources provide health status, metrics, and remote actions for operational monitoring
  • In BPM - Resources are tied to Services in process steps, bringing real-time operational status into business process diagrams
  • Bidirectional visibility - Click a Resource in a Monitor View to see which BPM processes it belongs to, or click a BPM step to see the underlying Resources and execute remote actions

This dual perspective means:

✅ Operations teams monitor Resources for health and performance
✅ Business users see the same Resources in context of their business processes
✅ Remote actions work in both views - Start/stop services from Monitor Views OR directly from BPM steps
✅ Single source of truth - One Resource, multiple visualizations for different audiences

graph TB subgraph "Monitoring Agent Discovers" MA[fal:fa-monitor-waveform Monitoring Agent] R[fal:fa-lightbulb-on Resource
SQL Server, Queue, API, Service] MA -->|Discovers & monitors| R end subgraph "Dual Usage" MV[fal:fa-display Monitor View
Operations perspective] SVC[fal:fa-gear Service
Repository Model] BPM[fal:fa-project-diagram BPM Step
Business perspective] R -->|Included in| MV R -->|Tied to| SVC SVC -->|Placed in| BPM end subgraph "Self-Service Actions" USER1[fal:fa-user Operations Team
Monitor View] USER2[fal:fa-user Business User
BPM View] RA[fal:fa-wrench Remote Actions
Start/Stop/Restart] MV -->|Access| USER1 BPM -->|Access| USER2 USER1 -->|Execute| RA USER2 -->|Execute| RA end style R fill:#fff4e1 style MV fill:#e8f5e9 style BPM fill:#e1f5ff style RA fill:#f3e5f5

Diagram: Resources serve both operational monitoring (Monitor Views) and business visualization (BPM)—connected through Services in the Repository Model

The actual Resource has one of the following states at any given moment which represents it evaluated condition:

State Status Description
OK Online All's well; The Resource is operational
Warning Warning state raised One or more minor problems are detected
Error Error state raised One or more major problems are detected
Unavailable Resource not available Used to indicate an error/fatal condition usually since the Monitoring Agent Configuration or resource unavailable or can't be reached from the Monitoring Agent. Also, some Monitoring Agents use this state to indicate bad configuration, or inability to evaluate the Resource
Connection Error Monitoring Service fails to communicate with the Monitoring Agent Service is offline (server is shutdown/rebooting)
Connectivity issues (bad network)
Invalid Monitoring Agents configuration
Invalid Remote Configuration

State / Status Code colors and order:
4

Examples:
Examples

The following properties are available on a Resource:

Property Description
Name The name of the Resource
Description The user-friendly description about the Resource
Web Site Provides the ability for a link to additional external documentation
Monitoring Agent Configuration The name of the Monitoring Agent Configuration the Resource origins from
Application The name of the Application
Category The name of the Category

Expected State

All resources can be reconfigured to provide a different outcome when evaluating the current state. For example, a disabled SQL Job would normally be considered an error. By setting the expected State of the Resource different outcome is the result for the current state.

The opposite can also hold true, for example a Receive Location in BizTalk is supposed to be stopped due to some ongoing problem pending solution. Meanwhile, the Receive Location should be stopped.
Expected state

From inside a Monitor View a resource with reconfigured expected state is displayed with a coloured dot indicating the real state. Expected state icon

Note

The LogText should not change over time for a resource that do not change its state. This is due to the caching mechanism trying to conserve bandwidth and costs when using service bus relaying.

State / Status Code values

Internally within Nodinite the following Status Code values are being used:

State Status Code values
OK 0
Warning 1
Error 2
Unavailable 3
Connection Error 4

Next Step

Add or manage Resource
Add or manage Monitor View
Services - Understand how Resources connect to BPM
Business Process Models (BPM) - See Resources in business context

Resource Organization:

Monitoring & Actions:

BPM Integration:

Security: