Monitoring

C4 Diagrams is part of experimental builds. To access this capability, contact your sales representative.

Architecture Diagrams in Nodinite are not static pictures — Service-type nodes on every diagram carry live operational health sourced directly from the Monitoring system. When a Service bound to a C4 node has one or more Resources, the node displays the real-time aggregated health state: green for OK, yellow for warning, red for error. You can also execute Remote Actions directly from within the diagram without switching to a Monitor View.

✅ Live health indicators (OK / Warning / Error) on Service-type nodes in any C4 diagram
✅ Click a Service node to see its linked Resources and individual states
✅ Execute Remote Actions without leaving the architectural view
✅ Same feature model as the Integration Landscape — consistent experience across all visual tools

Only Service-type nodes carry monitoring health. System nodes (C4Type = Person / InternalSystem / ExternalSystem) represent platform-level or external entities and do not have Resources. Monitoring health lives at the Service level because that is where Nodinite tracks operational execution.

How Service Nodes Get Their Health

The connection between a C4 diagram node and live operational data follows the same path used by every operational view in Nodinite:

A C4 Service node is bound 1:1 to a Service in the Repository. That Service has zero or more Resources. A Monitoring Agent polls each Resource and updates its state. Nodinite aggregates all Resource states for the Service and overlays the worst-case health badge on the node.

Health State Aggregation

When a Service has multiple Resources, the node displays the worst-case status across all linked Resources:

Remote Actions from the Diagram

When a Service node shows a Warning or Error state, you do not need to navigate away to take action. Clicking the node opens the Service detail panel, which lists all linked Resources with their individual states. For each Resource, if Remote Actions are configured, an action menu appears inline.

Permission check: Remote Actions are gated by the same role-based permissions used in Monitor Views. If your account does not have the Execute Action permission for that Resource's Permission Set, the action menu is hidden.

Common actions available directly from a C4 diagram node:

• Restart service — restart a failed or degraded service component
• Purge queue — clear a message backlog causing queue depth warnings
• Details — view the Resource detail panel with metrics history
• Edit thresholds — adjust warning/error thresholds without leaving the diagram

The full set of available actions depends on the Monitoring Agent type and the Resource category — the same actions available in a Monitor View are available here.

Relationship to the Integration Landscape

The monitoring integration in C4 diagrams uses the exact same mechanism as the Integration Landscape. In the Integration Landscape, Systems and Services (Contracts are a simplified form of Service) show health indicators and support Remote Actions in the same way. If you are already familiar with monitoring in the Integration Landscape, the C4 diagram experience is identical.

The key difference is scope and audience: the Integration Landscape shows one integration scenario deeply; C4 diagrams show architectural structure across multiple systems and services in a single view.

Configuring Monitoring for a Service

Monitoring health in a C4 diagram requires no diagram-specific configuration. You configure monitoring at the Service and Resource level in the Repository, and every C4 diagram that binds a node to that Service automatically picks up the health state.

To enable monitoring on a Service that appears in your C4 diagrams:

1. Open the Service in the Repository
2. Navigate to Resources — add one or more Resources using the relevant Monitoring Agent
3. Configure thresholds — set OK/Warning/Error thresholds for each Resource
4. Ensure the Monitoring Agent is active — the agent must be running and polling for health states to appear
5. Return to your C4 diagram — the node health badge updates automatically on the next polling cycle

Resources are managed in Administration → Monitor Management → Resources. For guidance on adding Resources to a Service, see What is a Resource?.

Relationship to BPM Monitoring

Business Process Modeling (BPM) offers the same monitoring integration — Services placed on a BPM diagram show Resource health and support Remote Actions in the same way. Choose the view that best fits the question you are answering:

All three views share the same underlying Resource health data — no duplication or extra configuration is required.

Next Step

Integration Landscape — monitoring in the landscape uses the same mechanism
Remote Actions — understand the permission model and available action types
What is a Resource? — learn how Resources connect to Services
Monitor Views — the dedicated operational monitoring interface

Related Topics

Architecture Diagrams Overview
BPM — Monitor and Act — the same feature in BPM diagrams
Monitoring — working with Monitor Views and Agents
Monitor Views — manage and monitor Resources in a composite view
Remote Actions — execute actions on monitored resources
Services — the Repository entity that owns Resources
C4 Designer — the interactive canvas for building C4 diagrams