dohertj2/ScadaBridge
1
0
Fork 0
Code Issues 15 Pull Requests Actions Packages Projects Releases Wiki Activity

AuditLog chain-head export: failures are log-only, no health counter #115

New Issue
Closed
opened 2026-11-09 23:32:37 -05:00 by dohertj2 · 1 comment
dohertj2 commented 2026-11-09 23:32:37 -05:00
Owner
Copy Link
Copy Source

Follow-up from #107 item 1 (c4d7ec9b). AuditChainHeadExportService logs an export failure (share offline, syslog collector unreachable) at Error and retries the same heads next tick, but nothing surfaces on the central health dashboard — the purge path has PurgeFailures, the head export has no counter. A sink that stays down silently stops the external anchor.

Proposal: an ExportFailures counter (or last-success timestamp) on AuditCentralHealthSnapshot, and consider a KPI for "months whose current head has not been exported for > 2 intervals". Also note: UDP syslog is fire-and-forget, so a dropped datagram is invisible by design — TCP is the recommended transport where that matters (documented).

Follow-up from #107 item 1 (`c4d7ec9b`). `AuditChainHeadExportService` logs an export failure (share offline, syslog collector unreachable) at Error and retries the same heads next tick, but nothing surfaces on the central health dashboard — the purge path has `PurgeFailures`, the head export has no counter. A sink that stays down silently stops the external anchor. Proposal: an `ExportFailures` counter (or last-success timestamp) on `AuditCentralHealthSnapshot`, and consider a KPI for "months whose current head has not been exported for > 2 intervals". Also note: UDP syslog is fire-and-forget, so a dropped datagram is invisible by design — TCP is the recommended transport where that matters (documented).
dohertj2 added the type:followuppriority:p3 labels 2026-11-09 23:32:37 -05:00
dohertj2 commented 2026-11-09 23:48:06 -05:00
Author
Owner
Copy Link
Copy Source

Fixed in 533414a1 (main). Head-export tick failures now increment counter scadabridge.audit.chain_head_export.failures (shared ScadaBridge meter) and update AuditChainHeadExportStatus; new /health/ready entry audit-chain-head-export (Host AuditChainHeadExportHealthCheck) is Degraded (HTTP 200) while the last tick failed or there has been no success for > 2 intervals, Healthy when disabled. UDP syslog fire-and-forget caveat + TCP recommendation documented. Evidence: AuditChainHeadExportServiceTests.FailedTick_RecordsMetricAndStatus_SuccessResetsConsecutive (MeterListener) and AuditChainHeadExportHealthCheckTests; mutation-proved (removing RecordFailure fails it). Not done: a months-not-exported KPI on AuditCentralHealthSnapshot (the staleness check covers the silent-anchor case).

Fixed in 533414a1 (main). Head-export tick failures now increment counter scadabridge.audit.chain_head_export.failures (shared ScadaBridge meter) and update AuditChainHeadExportStatus; new /health/ready entry audit-chain-head-export (Host AuditChainHeadExportHealthCheck) is Degraded (HTTP 200) while the last tick failed or there has been no success for > 2 intervals, Healthy when disabled. UDP syslog fire-and-forget caveat + TCP recommendation documented. Evidence: AuditChainHeadExportServiceTests.FailedTick_RecordsMetricAndStatus_SuccessResetsConsecutive (MeterListener) and AuditChainHeadExportHealthCheckTests; mutation-proved (removing RecordFailure fails it). Not done: a months-not-exported KPI on AuditCentralHealthSnapshot (the staleness check covers the silent-anchor case).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
blocked
Blocked by dependency or external hold
 cross-repo
Needs coordinated change in another family repo (wire contract etc.)
 migrated
Migrated from a markdown backlog (2026-11 standardization)
 priority:p0
Must-have / blocking
 priority:p1
High priority
 priority:p2
Normal priority
 priority:p3
Low priority / nice to have
 type:bug
Defect in shipped behaviour
 type:debt
Technical debt / hygiene
 type:deploy-gate
Rollout/deploy/migration step not yet done on an environment
 type:docs
Documentation work
 type:feature
Feature implementation
 type:followup
Follow-up deferred from a plan, PR or gate
 type:infra
Infrastructure and scaffolding
 type:review-finding
Unfixed finding from an architecture/code review
 type:test
Test work
No Label priority:p3 type:followup
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
dohertj2 (dohertj2)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dohertj2/ScadaBridge#115
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?