13.6 Health and Observability Plane QoS Profile
Go To Phase 0 QoS Profile Model
The Health and Observability Plane QoS profile supports operational condition reporting.
Health and Observability Plane communication must allow implementation participants to report lifecycle state, availability, warnings, degradation, failure, recovery, and status reasons. The Phase 0 implementation uses this information to observe Node condition and support later deployment, testability, and Evidence planning.
Table 13-3: Health and Observability Plane QoS profile.
| QoS Concern | Phase 0 Treatment |
|---|---|
| Runtime Plane | FX Logical Health and Observability Plane |
| Example DDS Topic | Health.FX.NodeStatus |
| Communication purpose | Report lifecycle state, health condition, availability, warning, degradation, failure, recovery, timestamp, and status reason |
| Reliability expectation | Reliable or best-effort delivery as selected by Phase 0 for status reporting; selected choice must be documented |
| Durability expectation | Sufficient durability to allow status observers to understand current or recent Node condition where Phase 0 requires it |
| History expectation | Retain recent status reports needed for demonstration, troubleshooting, and review |
| Ordering expectation | Preserve order of status changes for a reporting Node where lifecycle sequence matters |
| Liveliness expectation | Support detection of unavailable or silent participants where Phase 0 requires it |
| Compatibility expectation | Status publishers and status consumers use compatible QoS profiles for Node status Topic |
| Traceability expectation | QoS profile traces to FX Node Status Communication Endpoint, FX Node Status, and FX Logical Health and Observability Plane |
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.