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.
23 lines
1.2 KiB
C#
23 lines
1.2 KiB
C#
namespace ZB.MOM.WW.ScadaBridge.HealthMonitoring;
|
|
|
|
public class HealthMonitoringOptions
|
|
{
|
|
/// <summary>Interval at which sites emit health reports to the central cluster.</summary>
|
|
public TimeSpan ReportInterval { get; set; } = TimeSpan.FromSeconds(30);
|
|
/// <summary>Duration of silence after which a site is classified as offline.</summary>
|
|
public TimeSpan OfflineTimeout { get; set; } = TimeSpan.FromMinutes(1);
|
|
|
|
/// <summary>
|
|
/// Offline timeout applied to the synthetic "central" site only. Real sites
|
|
/// emit frequent heartbeats that keep <c>LastHeartbeatAt</c> fresh, so the
|
|
/// normal <see cref="OfflineTimeout"/> only fires on genuine total loss. The
|
|
/// "central" self-report has no heartbeat source — its only signal is the
|
|
/// 30s <see cref="CentralHealthReportLoop"/>, so a single skipped/late
|
|
/// self-report (leader GC pause, brief stall, mid-failover before the new
|
|
/// leader's loop spins up) would flap it offline under the 60s site timeout.
|
|
/// A longer central grace gives the equivalent of "one missed report" that
|
|
/// the design doc grants real sites. Default: 3x the report interval.
|
|
/// </summary>
|
|
public TimeSpan CentralOfflineTimeout { get; set; } = TimeSpan.FromMinutes(3);
|
|
}
|