Health And Observability Plane

Return to Terms and Definitions

Discussion

The Health and Observability Plane supports operational awareness. It carries information about Node state, heartbeat, availability, degradation, failure, warning conditions, recovery progress, runtime metrics, and other observations that help operators, monitors, or automated processes understand system condition.

The Health and Observability Plane differs from the Control Plane. The Health and Observability Plane reports or exposes operational conditions. The Control Plane coordinates action. A health event may trigger a control-plane response, but the two planes remain conceptually distinct.

A later implementation profile may realize Health and Observability Plane interactions through status topics, metrics endpoints, logs, telemetry streams, monitoring APIs, dashboards, or captured evidence. Those mechanisms do not redefine the Health and Observability Plane.

Definition

Runtime Plane supporting observation of operational condition and behavior.

Source

Adapted from FX Demo Reference Architecture, Section 4.4.4, Health and Observability Plane; informed by FDIS-RA monitoring, signals, indicators, traceability, auditability, and governance concerns.

Note

The Health and Observability Plane is not the same as evidence. Health and observability information may become evidence when an evidence process captures, preserves, and traces it to a claim.

Example

A heartbeat record, Node status update, degraded-service notification, or runtime availability metric may belong to the Health and Observability Plane.