Integrated Monitoring from BPM

When Services in your BPM are linked to one or more Resources, Nodinite displays real-time monitoring status in the BPM, both in view mode and in the BPM Designer. The familiar lightbulb icon shows the accumulated worst-case state across all linked Resources—giving you instant operational visibility without leaving the process context.

You get the monitoring of Monitor Views, in the context of your BPM:

• Visual status indicators - Lightbulb icon shows worst-case Resource state in BPM view mode and the Designer
• Remote Actions - The same Remote Actions as in a Monitor View, directly from the BPM
• Knowledge Base Articles - Open the operator instructions and troubleshooting guides attached to the Resources behind each step
• Custom Metadata - Organization-specific properties on BPMs, Domains, Services, and Resources, shown on their View pages
• Statistics - Available through the View options, as in Monitor Views
• Role-based access - Self-service monitoring for business and technical users

Animated walkthrough: in BPM Log Search for the Order-to-Cash BPM, pick an order, click the lightbulb of Order Invoiced, open the Action menu of the Resource O2C - Failed Errors, and run Details, a read-only Remote Action.

Tip

Business users prefer business context? BPMs show the same Resources, with the same Remote Actions, as Monitor Views, but organized by business process instead of technical hierarchy.

Order-to-Cash BPM in the Designer: lightbulbs on the Services that have one or more linked Resources; the shapes themselves stay gray.

How Service Monitoring Works in BPM

1. Link Services to Resources

In the BPM Designer, you place Services in cells (Domain row × Step column). Each Service can be linked to one or more Resources:

Example

• Service: "Order Received" (in Sales Domain, Step 1)
• Linked Resources:
  • Azure Service Bus Queue orders-inbound-prod
  • BizTalk Receive Location OrderReceivePort
  • File System Directory \\fileserver\orders\incoming

2. Lightbulb Icon Shows Worst-Case State

When Services have linked Resources, the lightbulb icon appears in:

• BPM view mode - Next to Service name in the cell, when you open the BPM read-only
• BPM Designer - Next to Service name in the cell; the Service shapes stay gray, because no log data is applied
• ^{New 7.11} Search log events from a BPM - In the BPM Viewer next to the search result, on the Service's row in the event table and on its shape; here the steps take the Log Status Code color of the events, and the lightbulb keeps showing the worst Resource state

A grouped Log View does not show the lightbulb. Its rows show the Log Status Code of the logged events only. To see monitoring status and act on it, open the BPM in view mode or in the Designer.

Lightbulb Colors

The lightbulb takes the most severe state across all linked Resources. This page is the one home for how that color is worked out; other pages link here.

Lightbulb Color	State (status code)	Meaning	Example Scenario
Green	✅ OK (0)	All Resources OK	All queues, services, and endpoints running normally
Yellow	⚠️ Warning (1)	The most severe Resource is in Warning	Queue depth approaching threshold but not critical
Red	❌ Error (2)	The most severe Resource is in Error	BizTalk Receive Location stopped or Service Bus throttled
Light gray	🚫 Unavailable (3)	At least one Resource is Unavailable	The Monitoring Agent can't reach or evaluate the Resource, for example because of a bad agent configuration
Black	🚫 Connection Error (4)	At least one Resource is in Connection Error (agent source error)	The Monitoring Service can't communicate with the Monitoring Agent: the agent is offline, the network is down, or the agent configuration is invalid

The light gray and black shades keep an unreachable target (Unavailable) apart from an unreachable agent (Connection Error). The colors match the Resource states used in Monitor Views.

Which State Wins

• The highest status code wins. "Most severe" means the highest status code: Connection Error (4), then Unavailable (3), then Error (2), then Warning (1), then OK (0). Unavailable and Connection Error therefore outrank Error.
• Example: a Service with one Resource in Error and one Resource Unavailable shows a light gray lightbulb, not a red one. Click the lightbulb to see both Resources and their states.
• Expected State comes first. Each Resource's Expected State is applied before the comparison, the same as in Monitor Views: a Resource in Error whose expected state for Error is OK counts as OK.
• Deleted Resources are left out. A deleted Resource that is still linked to the Service doesn't affect the color.
• The color follows your Roles. When your Roles limit which Monitor Views you can see, Resources outside those Monitor Views are left out of the calculation; administrators count all Resources. Two users with different Roles can therefore see different colors on the same Service.

Clicking the lightbulb opens the dialog Resources for the 'Service' Service, with filters for Monitoring Agent, Category, and Application. It shows:

• All linked Resources with individual states and Log Texts
• An Action menu for each Resource, grouped as MONITOR VIEWS (the Monitor Views that hold it), RESOURCE (View Resource History, Articles), ADMINISTRATION (Edit Monitoring Agent, Edit Resource), and CONTROL CENTER (the Remote Actions the agent provides)
• The Knowledge Base Articles attached to each Resource, through Articles

Custom Metadata is not shown in the lightbulb dialog. Open it on the View page of the BPM, Service, or Resource, or from Mapify and the View custom metadata options.

3. Perform Remote Actions from BPM

The Remote Actions you can run from a BPM are the same as from a Monitor View. They are whatever the linked Resources provide, delivered dynamically by the Monitoring Agents. There are thousands of them across agents and they change as agents are updated, so the list depends on the Resource—for example, start or stop a Windows service.

Example Workflow

1. User opens a grouped Log View for the Order-to-Cash process
2. Sees that order PIC-20261009-1644-0010 has an error Log Status Code at the "Confirmation Sent" milestone
3. Opens the Order-to-Cash BPM in view mode and sees a red lightbulb next to the "Confirmation Sent" Service
4. Clicks the lightbulb → the Resources dialog for the Service shows which Resource is in Error state
5. Picks a Remote Action from the Action menu of that Resource → Nodinite runs it via the Monitoring Agent
6. The lightbulb turns green once all linked Resources are OK again

The Action menu groups Monitor Views, Resource history and Articles, administration links, and Control Center, where the Remote Actions this agent provides for the Resource appear (here, for an IIS Application Pool that the Windows Server agent monitors: Details, Start, Stop, and Recycle).

^{New 7.11} To skip the switch, search from the BPM: the search result and the BPM, with its lightbulbs, appear side by side on one page.

No infrastructure access required - Users perform operations through Nodinite without RDP, VPN, or Azure Portal credentials.

4. Access Knowledge Base Articles

From a BPM you reach Knowledge Base Articles two ways:

• Through the lightbulb: the Resources dialog shows the Articles of each linked Resource, the same way as from the Integration Landscape.
• ^{New 7.12} Through the context menu: right-click a Service or a Domain (a lane) in the BPM Viewer. The menu shows its name with its type and id, View, and Articles (n). With one Article, Articles (1) opens it directly; with several, Articles (n) opens a submenu with one item per Article. The Article opens in a floating reader over the page, with Open full article and the option Open Articles in a new tab by default. Sub-processes have no Articles item. You link an Article to a Service or Domain on the Article's Repository entity cards or on the entity's Articles card. The menu lists the Articles only when your Role may read Articles.

The context menu of a Domain, here next to a search result; a Service's context menu has the same Articles submenu.

Animated walkthrough: right-click the Finance lane, point to Articles (2), and click an Article; it opens in the floating reader on top of the BPM.

Article Types

• Operator instructions - Step-by-step recovery procedures
• Troubleshooting guides - Common errors and resolutions
• Escalation procedures - When to contact support, who to escalate to
• SLA documentation - Expected response times, business impact
• Change logs - Recent configuration changes, deployment notes

Example Article: Order Receiver Queue Full

1. Check queue depth: Get-AzServiceBusQueue -ResourceGroupName prod -NamespaceName orders-ns -Name orders-inbound-prod
2. Verify downstream service health (Order Entry service)
3. If downstream is healthy, increase throughput or purge invalid messages
4. If downstream is stopped, restart via Remote Actions
5. Escalate to the Platform Team if the issue persists beyond the agreed SLA

The lightbulb of a Service shows only the Articles of the Resources linked to that Service; the context menu shows the Articles linked to the Service or Domain itself.

5. Leverage Custom Metadata for Fine-Grained Control

With hundreds of processes, Custom Metadata provides organization-specific attributes for Services, Resources, and entire BPMs:

Common Custom Metadata Fields

Field Name	Purpose	Example Value
Owner	Process/service owner	"John Smith (Finance Team)"
Team	Responsible team	"Integration Platform Team"
BusinessContact	Business stakeholder	"Jane Doe (Sales Ops Manager)"
SLA	Service level agreement	"99.5% uptime, <15 min MTTR"
EscalationPath	Who to contact	"Team Lead → Manager → Director"
CostCenter	Billing department	"CC-12345 (Sales Division)"
Criticality	Business importance	"P1 - Revenue impacting"
MaintenanceWindow	Allowed downtime	"Sundays 2-6 AM UTC"
ComplianceTag	Regulatory requirements	"GDPR, SOX, PCI-DSS"
DeploymentGroup	Release cadence	"Monthly Patch Cycle"

Benefits

• Search and filter - Find all P1 services owned by Finance Team
• Reporting - Export filtered results by ComplianceTag for compliance reviews
• Ownership clarity - Know who to contact when a Service fails

Example Use Case: Many BPMs Across the Organization

Instead of searching through diagrams, filter by:

• Owner: "Integration Team" - Show the BPMs owned by the Integration Team
• Criticality: "P1" - Show the revenue-critical processes that need round-the-clock monitoring
• ComplianceTag contains "SOX" - Show the processes that need Sarbanes-Oxley audit trails

Custom Metadata makes managing hundreds of processes practical and scalable.

Monitoring in the BPM vs. Grouped Log View

The BPM shows the health of the systems behind each step; a grouped Log View shows what happened to each transaction. Use them together.

BPM View Mode and Designer

When to Use

Checking and restoring the health of a process, design, documentation

What You See

• All Services in swimlane diagram (Domain rows × Step columns)
• Lightbulb icon next to each Service linked to Resources
• Real-time accumulated state (worst-case across linked Resources) on the lightbulb; in the Designer, with no log data applied, the shapes stay gray
• When the BPM is opened from a Log View, the shapes show the Log Status Code of the transaction instead, and the lightbulb keeps showing the Resource state
• Click lightbulb → Resource details panel with Remote Actions and Knowledge Base Articles

Best For

• Architects designing new processes
• Operations teams troubleshooting failed steps
• Business stakeholders checking overall process health

Grouped Log View

When to Use

Troubleshooting specific transactions, drilling into log events

What You See

• Milestone-based log events for a specific transaction (Order ID, Invoice Number, etc.)
• Services shown as milestones with timestamps
• Each milestone row shows the Log Status Code of its logged events, not the monitoring status of the Resources
• Log events below each milestone showing detailed execution history

Best For

• Support teams investigating why order PIC-20261009-1644-0010 failed at "Confirmation Sent"
• Compliance audits requiring full transaction history
• Root-cause analysis for specific incidents

Find the failed step in the grouped Log View, then open the BPM in view mode or the Designer to check the health of the Services behind it and act.

^{New 7.11} When users search log events from a BPM, the result and the BPM appear side by side, with the same lightbulb and Resources modal in the BPM.

What each user sees depends on their Roles: a Resource linked to a Service shows only if the Resource is in at least one Monitor View the user's role can access. Remote Actions and Knowledge Base Articles require their own permissions.

Monitor View and BPM Compared

A BPM gives you the monitoring of a Monitor View in the context of a business process:

Feature	Monitor View	BPM (view mode and Designer)
View Resource status	✅ Yes	✅ Yes (via lightbulb)
Perform Remote Actions	✅ Yes	✅ Yes, the same actions
Access Knowledge Base Articles	✅ Yes	✅ Yes, for the linked Resources, and New 7.12 for Services and Domains from the context menu
View Custom Metadata	✅ Yes	✅ Yes, on View pages and from Mapify
See monitoring statistics	✅ Yes	✅ Yes, through the View options
Configure alerts	✅ Yes, with Alarm Plugins	❌ No
Role-based security	✅ Yes	✅ Yes, through Monitor View access

Auto Healing belongs to neither: the Monitoring Service runs it in the background, independent of Monitor Views and BPMs.

A grouped Log View shows the Log Status Code per milestone instead; open the BPM to use these monitoring features.

The difference: Monitor Views organize by technical hierarchy (Applications, Categories, Resources). BPMs organize by business process (Domains, Steps, Services). Same Resources and Remote Actions, different organizational lens.

Prerequisites

Important

To enable monitoring in BPM:

1. Monitoring Agents - Install and configure agents for your platforms (BizTalk, Azure, databases, file systems)
2. Resources - Resources are automatically created by Monitoring Agents when they discover monitorable entities (queues, services, endpoints, etc.)
3. Monitor Views - Include the Resources in at least one Monitor View that the users' Roles can access; a Resource that is in no Monitor View for the user doesn't show in the BPM
4. Services - Create Services in Repository Model
5. Link Services to Resources - Edit each Service and add Resources in its Resources panel

Without linked Resources, Services will not show the lightbulb indicator.

Best Practices

Link All Services to Resources

• ✅ Do link Services to monitoring Resources - Enables lightbulb status in BPM view mode and the BPM Designer
• ✅ Link multiple Resources per Service - Shows worst-case state (most critical issue bubbles up)
• ❌ Don't leave Services unmonitored - Users won't have operational visibility or Remote Actions

Use Custom Metadata for Organization-Specific Attributes

• ✅ Define Owner field - Know who to contact when Service fails
• ✅ Define SLA field - Document expected uptime and response times
• ✅ Define EscalationPath field - Document who to escalate to
• ✅ Mark criticality - Prioritize P1 services in dashboards and alerts
• ❌ Don't rely on memory - Hundreds of processes require documented Custom Metadata

Combine BPM and Monitor Views

• ✅ BPM for business stakeholders - Process-oriented view with business context
• ✅ Monitor Views for operations teams - Technical hierarchy view with same Resources
• ✅ Both - Different audiences, same underlying monitoring data

Example

• BPM: "Order-to-Cash Process" - Business stakeholders see all 7 steps with lightbulb status
• Monitor View: "Production Azure Resources" - Ops team sees all Azure Resources across all BPMs

Both access the same "Order Receiver Queue" Resource with identical Remote Actions and Knowledge Base Articles.

Document Troubleshooting in Knowledge Base Articles

• ✅ Write operator instructions - Empower front-line support to resolve issues
• ✅ Include escalation procedures - When to escalate, who to contact
• ✅ Attach Articles to Resources - They show in the BPM (through the lightbulb), the Integration Landscape, and Monitor Views
• ❌ Don't rely on tribal knowledge - Staff turnover causes lost expertise

Next Steps

What is the BPM Designer - Create BPMs with Services and monitoring
Add or manage BPM - Step-by-step: monitor Resources and run Remote Actions from a BPM
Services - Define Services and link to Resources
Resources - Set up monitored Resources
Remote Actions - Configure available actions
Knowledge Base Articles - Write troubleshooting guides
Custom Metadata - Add organization-specific fields

Related Topics

Monitor Views - Technical-hierarchy monitoring view
Business Process Model (BPM) - Complete BPM overview
End-to-End Process Tracking - Correlate log events across systems
Search log events from a BPM - Search, result, and BPM with monitoring on one page
Roles - Role-based access control
Alarm Plugins - Alert configuration for Monitor Views
Auto Healing - Automatic Remote Actions run by the Monitoring Service