8.11 FX Health and Observability Node Mapping
Go To Mapping from FX Logical Nodes to Implementation Artifacts
The FX Health and Observability Node maps to the Phase 0 implementation artifact that observes and reports the implementation Node condition.
The implementation artifact performs or supports the Health Reporting Role. It receives or collects implementation representations of FX Node Status, observes lifecycle-state reports, records warnings or degraded conditions, and supports Control Plane or audit/provenance interaction when Phase 0 requires those relationships.
Table 8-9: FX Health and Observability Node implementation mapping.
| Mapping Concern | Phase 0 Implementation Treatment |
|---|---|
| FX logical Node | FX Health and Observability Node |
| Primary Node Role | Health Reporting Role |
| Primary Runtime Plane | FX Logical Health and Observability Plane |
| Supporting Runtime Planes | FX Logical Control Plane; FX Logical Audit and Provenance Plane |
| Primary implementation responsibility | Observe and report the implementation Node condition. |
| Primary DDS interactions | Subscribe to or publish through the DDS Topic that realizes the FX Node Status Endpoint. |
| Primary data artifact | IDL and a generated type representing FX Node Status. |
| Supporting artifacts | Health helper module, logging helper, lifecycle-state conventions, and traceability metadata. |
| Traceability expectation | Implementation artifact traces to the FX Health and Observability Node, Health Reporting Role, FX Node Status Endpoint, and FX Node Status. |
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.