fix(r2-10): register the tracker's production reader on driver nodes + wiring guard
This commit is contained in:
@@ -70,6 +70,13 @@ public static class DriverFactoryBootstrap
|
||||
logger: sp.GetService<ILoggerFactory>()?.CreateLogger("ZB.MOM.WW.OtOpcUa.Core.Resilience.DriverCapabilityInvokerFactory"));
|
||||
});
|
||||
|
||||
// The tracker's operator-facing reader: a periodic DPS publisher that mirrors each snapshot to the
|
||||
// AdminUI resilience panel (R2-10 — closes the "tracker fed by everything, read by nothing" gap).
|
||||
// Lives on driver nodes exactly where the tracker exists. The lazy Func<ActorSystem> is idempotent
|
||||
// with the one Program.cs registers for the alarm-command router.
|
||||
services.TryAddSingleton<Func<Akka.Actor.ActorSystem>>(sp => () => sp.GetRequiredService<Akka.Actor.ActorSystem>());
|
||||
services.AddHostedService<DriverResilienceStatusPublisherService>();
|
||||
|
||||
// Driver nodes also carry the probe set so a fused admin,driver node has it; the admin-only
|
||||
// case is covered by Program.cs calling AddOtOpcUaDriverProbes() in the hasAdmin block.
|
||||
services.AddOtOpcUaDriverProbes();
|
||||
|
||||
Reference in New Issue
Block a user