Cephalon.Observability.NatsDependencies
เนื้อหานี้ยังไม่ได้แปลเป็นภาษาไทย แสดงเป็นภาษาอังกฤษแทน
Maturity:
M0· Ownership: taxonomy-only · Family:observability· See audit, matrix.
Cephalon.Observability.NatsDependencies is the reusable dependency-health companion package for NATS brokers and clusters.
What it owns
Section titled “What it owns”Engine:Observability:DependencyHealth:Natsoption binding- reusable NATS
CONNECTplusPING/PONGprobe flow - token or username/password authentication wiring for broker reachability checks
- diagnostics conventions and runtime dependency-health contributions for NATS endpoints
Main surfaces
Section titled “Main surfaces”Configuration/NatsDependencyDefinition.csConfiguration/NatsDependencyHealthOptions.csHosting/NatsDependencyHealthServiceCollectionExtensions.cs
Source structure
Section titled “Source structure”ConfigurationHostingServices
How it fits
Section titled “How it fits”This package stays outside Cephalon.Engine and turns configured NATS endpoints into IDependencyHealthContributor data. Hosts keep the shared runtime health and readiness semantics from the engine, while this companion handles the provider-specific wire exchange: read the initial INFO line, send CONNECT, and verify a successful PING/PONG round-trip. Pair it with Cephalon.Eventing when a host wants broker-aware operational checks without pushing NATS socket details into the engine core.
This pack can grow across NATS-native protocol semantics such as richer auth modes, TLS controls, server-list handling, and broker reachability checks. If future work needs deeper workload semantics above the transport layer, keep that split deliberate instead of silently turning the baseline NATS probe pack into a product-specific runtime.