From 0dd3be0bd8bc7852e6b37f4d85d6cd9fd4a82afe Mon Sep 17 00:00:00 2001 From: Joseph Doherty Date: Mon, 18 May 2026 23:21:23 -0400 Subject: [PATCH] docs(notification-outbox): trim Site Event Logging notification row, de-duplicate rationale --- docs/requirements/Component-SiteEventLogging.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/requirements/Component-SiteEventLogging.md b/docs/requirements/Component-SiteEventLogging.md index f0f3501..b568b5a 100644 --- a/docs/requirements/Component-SiteEventLogging.md +++ b/docs/requirements/Component-SiteEventLogging.md @@ -25,7 +25,7 @@ Site clusters (event recording and storage). Central cluster (remote query acces | Data Connection Status | Connected, disconnected, reconnected (per connection) | | Store-and-Forward | Message queued, delivered, retried, parked | | Instance Lifecycle | Instance enabled, disabled, deleted | -| Notification | Site→central forward failure, long-buffered notification (notification still in the site Store-and-Forward buffer past a threshold). Routine enqueue and successful forward events are **not** logged — central holds the authoritative `Notifications` table; site-side logging covers only the in-transit blind spot when the site cannot reach central. | +| Notification | Site→central forward failure, long-buffered notification (still in the site buffer past a threshold) | ## Event Entry Schema @@ -70,5 +70,5 @@ Each event entry contains: - **All site subsystems**: Event logging is a cross-cutting concern — any subsystem that produces notable events calls the Event Logging service. - **Communication Layer**: Receives remote queries from central and returns results. - **Central UI**: Site Event Log Viewer displays queried events. -- **Store-and-Forward Engine**: Its notification path (the site→central forward of script-generated notifications) reports forward failures and long-buffered notifications as Notification-category events. Routine enqueue/forward-success events are deliberately not logged — the central Notification Outbox's `Notifications` table is the authoritative audit record; site-side logging covers only the in-transit blind spot when central is unreachable. +- **Store-and-Forward Engine**: Its notification path (the site→central forward of script-generated notifications) reports forward failures and long-buffered notifications as Notification-category events. Routine enqueue and forward-success events are deliberately not logged — central's authoritative `Notifications` table (owned by the Notification Outbox component) is the audit record of record; site-side logging covers only the in-transit blind spot when central is unreachable. - **Health Monitoring**: Script error rates and alarm evaluation error rates can be derived from event log data.