Differences

This shows you the differences between two versions of the page.

--- dido:99_annexes:annex-b-terms-and-definitions:h:health_and_observability_plane [2026/07/11 11:14] – ↷ Page moved from dido:99_annexes:99_annexes:annex-b-terms-and-definitions:h:health_and_observability_plane to dido:99_annexes:annex-b-terms-and-definitions:h:health_and_observability_plane nick_dido
+++ dido:99_annexes:annex-b-terms-and-definitions:h:health_and_observability_plane [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 1: / Line 1: @@
 ====== Health And Observability Plane ======
-[[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]]
+[[dido:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]]
 ===== Discussion =====
-The Health and Observability Plane supports operational awareness. It carries information about [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:n:node|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 supports operational awareness. It carries information about [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|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 realise 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.
+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 behaviour.//
+//Runtime Plane supporting observation of operational condition and behavior.//
 ===== Source =====
@@ Line 25: / Line 25: @@
 ===== Example =====
-A heartbeat record, [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:n:node|Node]] status update, degraded-service notification, or runtime availability metric may belong to the Health and Observability Plane.
+A heartbeat record, [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]] status update, degraded-service notification, or runtime availability metric may belong to the Health and Observability Plane.