Joseph Doherty
7b0b9c7365
Solution + 23 src projects + 26 test projects renamed; folders, csproj, namespaces, and ScadaLinkDbContext/ScadaBridgeDbContext class updated. ActorSystem "scadalink" → "scadabridge", Akka seed-node URLs migrated. SQL roles/logins, LDAP domains, CLI command name, and CLI config dir (~/.scadalink → ~/.scadabridge) also renamed. Build green; 5 Host.Tests fail awaiting SQL login rename in next commit. Pre-existing StaleTagMonitor timing flakes unchanged. Rename script committed at tools/rename-to-scadabridge.sh.
62 lines
3.0 KiB
C#
62 lines
3.0 KiB
C#
using ZB.MOM.WW.ScadaBridge.AuditLog.Payload;
|
|
|
|
namespace ZB.MOM.WW.ScadaBridge.AuditLog.Central;
|
|
|
|
/// <summary>
|
|
/// Audit Log (#23) M6 Bundle E (T9) — bridges
|
|
/// <see cref="IAuditRedactionFailureCounter"/> (incremented by
|
|
/// <see cref="DefaultAuditPayloadFilter"/> every time a header / body / SQL
|
|
/// parameter redactor stage throws and the filter has to over-redact the
|
|
/// offending field) into <see cref="AuditCentralHealthSnapshot"/> so the
|
|
/// failure surfaces on the central health surface as
|
|
/// <c>AuditCentralHealthSnapshot.AuditRedactionFailure</c>.
|
|
/// </summary>
|
|
/// <remarks>
|
|
/// <para>
|
|
/// <b>Site vs central.</b> M5 Bundle C wired the SITE-side bridge
|
|
/// (<see cref="ZB.MOM.WW.ScadaBridge.AuditLog.Site.HealthMetricsAuditRedactionFailureCounter"/>),
|
|
/// which routes increments into the site health report payload's
|
|
/// <c>AuditRedactionFailure</c> field. That handles redactor failures on the
|
|
/// site SQLite hot-path (FallbackAuditWriter). M6 Bundle E (T9) adds the
|
|
/// MIRROR bridge here so the same payload filter — when it runs on the
|
|
/// central <see cref="CentralAuditWriter"/> /
|
|
/// <see cref="AuditLogIngestActor"/> paths — surfaces its failures on the
|
|
/// central dashboard rather than disappearing into a NoOp.
|
|
/// </para>
|
|
/// <para>
|
|
/// <b>Registration shape.</b> Site composition roots call
|
|
/// <see cref="ServiceCollectionExtensions.AddAuditLogHealthMetricsBridge"/>,
|
|
/// which overrides the binding with the site bridge. Central composition
|
|
/// roots call <see cref="ServiceCollectionExtensions.AddAuditLogCentralMaintenance"/>,
|
|
/// which overrides with this central bridge. A node never wears both hats —
|
|
/// site and central are distinct host roles — so the two bridges never
|
|
/// fight over the same binding at runtime.
|
|
/// </para>
|
|
/// <para>
|
|
/// <b>Why not a thin wrapper around the snapshot directly?</b> The snapshot
|
|
/// itself <i>could</i> be the bound implementation (it already implements
|
|
/// <see cref="IAuditRedactionFailureCounter"/>), but a dedicated class makes
|
|
/// the central-vs-site asymmetry explicit at the DI boundary — readers of
|
|
/// <see cref="ServiceCollectionExtensions.AddAuditLogCentralMaintenance"/>
|
|
/// see "site → site bridge, central → central bridge", matching the
|
|
/// <see cref="ZB.MOM.WW.ScadaBridge.AuditLog.Site.HealthMetricsAuditRedactionFailureCounter"/>
|
|
/// shape one-for-one.
|
|
/// </para>
|
|
/// </remarks>
|
|
public sealed class CentralAuditRedactionFailureCounter : IAuditRedactionFailureCounter
|
|
{
|
|
private readonly AuditCentralHealthSnapshot _snapshot;
|
|
|
|
/// <summary>
|
|
/// Initializes a new <see cref="CentralAuditRedactionFailureCounter"/> backed by the supplied snapshot.
|
|
/// </summary>
|
|
/// <param name="snapshot">The central health snapshot that accumulates the redaction failure count.</param>
|
|
public CentralAuditRedactionFailureCounter(AuditCentralHealthSnapshot snapshot)
|
|
{
|
|
_snapshot = snapshot ?? throw new ArgumentNullException(nameof(snapshot));
|
|
}
|
|
|
|
/// <inheritdoc/>
|
|
public void Increment() => ((IAuditRedactionFailureCounter)_snapshot).Increment();
|
|
}
|