- 7 minutes to read

Integrated Monitoring

Monitor service health and take action directly from your process diagram—no infrastructure access required

Integrated Monitoring is Nodinite BPM's truly unique capability that sets it apart from all other BPM tools. It combines visual process modeling with real-time operational monitoring and remote actions—enabling you to see service health, diagnose failures, and take corrective action without leaving the BPM or accessing underlying infrastructure.

This is living documentation at its best: Your BPM isn't just a diagram—it's an operational control center.

The Problem: Disconnected Monitoring and Documentation

Traditional BPM tools create static diagrams with zero operational insight:

❌ No visibility into service health - Can't see which services are running, stopped, or failing
❌ Switching between tools - BPM in one tool, monitoring in another (Azure Portal, BizTalk Admin, custom dashboards)
❌ Manual troubleshooting - Identify problem in logs, then manually connect to infrastructure to restart services
❌ Access control complexity - Operations teams need infrastructure credentials to restart services
❌ Slow incident response - MTTR increases due to tool-switching and access delays

Visio, draw.io, Azure Business Process Tracking, Kovai Atomic Scope - none of these offer integrated monitoring.

The Solution: Real-Time Monitoring in BPM

Nodinite BPM embeds monitoring directly into the process diagram:

✅ See service health in real-time - Each service in BPM shows operational status (Running, Stopped, Disabled, Error)
✅ Trigger remote actions - Start, Stop, Enable, Disable services directly from BPM—no infrastructure access required
✅ Unified operational view - Monitor on-premise BizTalk, Azure Logic Apps, databases, file systems, APIs—all in one BPM
✅ Role-based access - Grant operations teams BPM access without exposing infrastructure credentials
✅ Faster incident response - From problem identification to service restart in seconds, not minutes
✅ Audit trail for actions - All remote actions logged for compliance and troubleshooting

This is unique to Nodinite BPM.

How It Works

1. Services Linked to Resources

In the BPM Designer, each Service in a cell is linked to one or more Resources:

Service: "Order Processing Logic App"
Resource: Azure Logic App order-processing-prod
Monitoring Agent: Azure Monitoring Agent
Operational Status: ✅ Running

2. Monitoring Agents Report Status

Monitoring Agents poll resources and report status to Nodinite:

{
  "resourceId": "guid-order-processing",
  "resourceName": "order-processing-prod",
  "status": "Running",
  "availability": 99.8,
  "lastChecked": "2026-02-06T14:45:30Z"
}

Supported resource types:

  • BizTalk Send/Receive Locations, Orchestrations, Host Instances
  • Azure Logic Apps, Function Apps, Service Bus Queues
  • Databases (SQL Server, Oracle, MySQL)
  • File system directories
  • Web services and APIs
  • Custom resources via REST API

3. BPM Displays Real-Time Status

Each service in the BPM shows operational status:

Visual Indicators

  • 🟢 Running - Service operational
  • 🔴 Stopped - Service stopped (intentional or failure)
  • ⚪ Disabled - Service disabled (maintenance mode)
  • ⚠️ Error - Service in error state
  • ❓ Unknown - Monitoring agent not reporting

Availability Metrics

  • 99.9% - Last 24 hours
  • 98.5% - Last 7 days
  • 97.2% - Last 30 days

4. Users Trigger Remote Actions

Right-click any service in the BPM Designer or Monitor View to trigger Remote Actions:

Available Actions

  • Start - Start a stopped service
  • Stop - Stop a running service
  • Enable - Enable a disabled service
  • Disable - Disable a service (maintenance mode)
  • Restart - Stop and start in one action
  • Clear Cache - Clear service-level cache
  • Custom Actions - Resource-specific actions (e.g., "Purge Queue", "Reset Connection")

Action Execution

  1. User clicks "Start" on stopped service
  2. Nodinite sends command to Monitoring Agent
  3. Monitoring Agent executes action on infrastructure (BizTalk Admin API, Azure Resource Manager API, etc.)
  4. Status updated in real-time
  5. Action logged to audit trail

No infrastructure credentials required - Nodinite handles authentication via Monitoring Agents.

BPM - Monitor View Example
Monitor View showing real-time service health with remote actions available

Key Capabilities

Unified Multi-Platform Monitoring

Monitor all your integration platforms from a single BPM:

Platform Monitorable Resources Remote Actions
BizTalk Server Send/Receive Locations, Orchestrations, Host Instances Start, Stop, Enable, Disable, Restart
Azure Logic Apps Workflows, Connections Enable, Disable, Trigger Run
Azure Service Bus Queues, Topics, Subscriptions Purge Queue, Disable/Enable
Databases SQL Server, Oracle, MySQL availability Connection Test
File Systems Directory availability, file count Clear Directory (custom)
Web Services HTTP endpoint availability, response time None (monitoring only)
Custom Any resource via REST API Custom actions via API

This platform-agnostic approach eliminates vendor lock-in - monitor BizTalk today, Azure tomorrow, AWS next month.

Visual Process Health Assessment

The BPM provides instant operational insight:

  • All services green? - Process healthy, no action required
  • One service red? - Bottleneck identified, drill down for details
  • Multiple services red? - Infrastructure issue, escalate to operations
  • Warning indicators? - Degraded performance, proactive investigation needed

Business stakeholders see high-level process health without technical knowledge.
Operations teams see granular service status for troubleshooting.

Operational Dashboards with Monitor Views

Monitor Views provide role-specific operational dashboards:

"Production Monitoring Dashboard" - All production services across all processes
"Azure Integration Platform" - All Azure Logic Apps, Service Bus, Function Apps
"Finance Domain Services" - All services owned by Finance domain
"Critical Order-to-Cash Process" - All services for O2C BPM only

Each Monitor View shows:

  • Service operational status (Running, Stopped, Error)
  • Availability metrics (24h, 7d, 30d)
  • Last checked timestamp
  • Remote actions available
  • Link to related BPM for context

Proactive Alerting with Non-Events

Non-Events Monitoring detects missing or delayed BPM milestones:

Expected: Order-to-Cash process should receive order within 30 minutes of business hours start
Reality: No orders received after 45 minutes
Alert: "Missing milestone: Order entry expected but not logged"

Use cases:

  • Detect upstream system failures (no orders from CRM)
  • Identify process delays (payment authorization >5 minutes)
  • Ensure compliance (daily batch job must complete by 6AM)

Integration with Change Tracking

When services are started/stopped via BPM remote actions:

  1. Action logged to audit trail - Who, what, when, why
  2. State change recorded - Service state: Running → Stopped
  3. Notification sent - Email/Teams to responsible team
  4. Change history viewable - Filter by service, user, date range

Compliance benefit: Complete audit trail showing all operational changes made via BPM.

Example: Incident Response Workflow

Scenario: Payment processing failing in Order-to-Cash process

Traditional Approach

  1. Alert received: "Payment failures increasing" - 2 minutes
  2. Identify failing service: Check logs, Azure Portal - 5 minutes
  3. Access infrastructure: Request credentials or escalate - 15 minutes
  4. Diagnose issue: Review Logic App run history - 10 minutes
  5. Restart service: Azure Portal → Logic App → Disable/Enable - 3 minutes
  6. Verify resolution: Wait for next payment, check logs - 5 minutes

Total MTTR: 40 minutes

Nodinite Approach

  1. Alert received + service identified: BPM shows red "Payment Processing" step - 30 seconds
  2. Diagnose issue: Click step → view log events → see error "Connection pool exhausted" - 1 minute
  3. Restart service: Right-click service in BPM → "Restart" - 10 seconds
  4. Verify resolution: BPM shows green status, next payment succeeds - 30 seconds

Total MTTR: 2 minutes 10 seconds (95% reduction)

Prerequisites

Important

To enable Integrated Monitoring:

  1. Monitoring Agents - Install and configure monitoring agents for each platform (BizTalk, Azure, database, file system)
  2. Resources - Define resources in Nodinite repository (map to physical infrastructure)
  3. Services - Link services to resources in BPM Designer
  4. Permissions - Grant users appropriate roles for remote actions (Administrator, Operator, Viewer)

Without Monitoring Agents and Resources, services will not show operational status.

Best Practices

✅ Do link services to resources - Enables integrated monitoring
❌ Don't leave services unmonitored - Defeats the purpose of living documentation

Even read-only services (no remote actions) benefit from availability monitoring.

Configure Meaningful Remote Actions

Enable remote actions appropriate for each resource type:

  • Production services: Start, Stop (not Delete)
  • Test services: Start, Stop, Disable, Clear Cache
  • Critical services: Start only (prevent accidental Stop)

Use Monitor Views for Role-Based Dashboards

Create Monitor Views for different audiences:

  • "NOC Dashboard" - All production services, grouped by availability
  • "Development Support" - All test/dev services, grouped by developer
  • "Business Stakeholder View" - Critical revenue-impacting processes only

Document Remote Action Reasons

When executing remote actions, add comments:

  • "Restarting due to connection pool exhaustion"
  • "Stopping for maintenance window - deploy v2.1"
  • "Disabling temporarily - upstream system outage"

These comments appear in audit trail for compliance.

Next Steps

Resources – Define resources for monitoring integration points
Monitoring Agents – Install agents for BizTalk, Azure, databases, file systems
Remote Actions – Configure available actions for each resource type
Monitor Views – Create role-specific operational dashboards

Business Process Model (BPM) – Complete BPM overview
What is the BPM Designer – Create visual process models with services
End-to-End Process Tracking – Correlate log events across systems
Services – Integration services that execute process steps
Non-Events Monitoring – Detect missing or delayed BPM milestones