8e5090edf3
Each of the four telemetry publish seams now also emits its DPS payload into the node-local ITelemetryLocalHub (Phase 5), leaving the existing DistributedPubSub publish untouched: - driver-health AkkaDriverHealthPublisher -> TelemetryItem.Health - resilience DriverResilienceStatusPublisherService -> TelemetryItem.Resilience - alerts ScriptedAlarmHostActor + DriverHostActor (native) -> TelemetryItem.Alarm - script-logs VirtualTagActor + DpsScriptLogPublisher -> TelemetryItem.Script DI services take the hub as a required ctor param; actors take an optional nullable hub threaded through their Props and the real spawn sites (DriverHostActor <- ServiceCollectionExtensions; VirtualTagActor/ScriptedAlarmHostActor <- DriverHostActor), so existing test Props constructions keep compiling and simply do not emit. The hub is a no-op until a gRPC client subscribes, so the emit is safe on every node. Claude-Session: https://claude.ai/code/session_01GASWkNEi68FSCtvr6rLoEW
49 lines
2.0 KiB
C#
49 lines
2.0 KiB
C#
using Akka.Actor;
|
|
using Akka.Cluster.Tools.PublishSubscribe;
|
|
using ZB.MOM.WW.OtOpcUa.Commons.Messages.Drivers;
|
|
using ZB.MOM.WW.OtOpcUa.Core.Abstractions;
|
|
using ZB.MOM.WW.OtOpcUa.Runtime.Telemetry;
|
|
|
|
namespace ZB.MOM.WW.OtOpcUa.Runtime.Drivers;
|
|
|
|
/// <summary>
|
|
/// Forwards <see cref="DriverHealth"/> transitions to the cluster-wide
|
|
/// <c>driver-health</c> DistributedPubSub topic. Consumed by the AdminUI
|
|
/// <c>DriverStatusSignalRBridge</c>.
|
|
/// </summary>
|
|
public sealed class AkkaDriverHealthPublisher : IDriverHealthPublisher
|
|
{
|
|
/// <summary>The DistributedPubSub topic name for driver-health snapshots — single source
|
|
/// of truth on the message contract itself.</summary>
|
|
public const string TopicName = DriverHealthChanged.TopicName;
|
|
|
|
private readonly ActorSystem _system;
|
|
private readonly ITelemetryLocalHub _hub;
|
|
|
|
/// <summary>Initializes a new instance of <see cref="AkkaDriverHealthPublisher"/>.</summary>
|
|
/// <param name="system">The Akka actor system used to resolve the DPS mediator.</param>
|
|
/// <param name="hub">The node-local live-telemetry hub each snapshot is also emitted into (Phase 5).</param>
|
|
public AkkaDriverHealthPublisher(ActorSystem system, ITelemetryLocalHub hub)
|
|
{
|
|
_system = system;
|
|
_hub = hub;
|
|
}
|
|
|
|
/// <inheritdoc />
|
|
public void Publish(string clusterId, string driverInstanceId, DriverHealth health, int errorCount5Min)
|
|
{
|
|
var msg = new DriverHealthChanged(
|
|
clusterId,
|
|
driverInstanceId,
|
|
health.State.ToString(),
|
|
health.LastSuccessfulRead,
|
|
health.LastError,
|
|
errorCount5Min,
|
|
DateTime.UtcNow);
|
|
DistributedPubSub.Get(_system).Mediator.Tell(new Publish(TopicName, msg));
|
|
// Phase 5: fan the same snapshot into the node-local live-telemetry hub (no-op until a gRPC
|
|
// client subscribes). The DPS publish above is unchanged — the hub is a strictly additive tap.
|
|
_hub.Emit(new TelemetryItem.Health(msg));
|
|
}
|
|
}
|