npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-grasp-mirror/docs/explanation/monitoring.md, branch masterUnnamed repository; edit this file 'description' to name the repository.
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-grasp-mirror/atom?h=master2026-01-09T21:12:51+00:00docs: integrate rejected events index into architecture documentation2026-01-09T21:12:51+00:00DanConwayDevDanConwayDev@protonmail.com2026-01-09T21:12:51+00:00urn:sha1:5fed2e2f32cfb15fff042a39f3ac82abe8948ca0
- Add rejected events index to architecture.md with two-tier system explanation
- Document NGIT_REJECTED_HOT_CACHE_DURATION_SECS and NGIT_REJECTED_COLD_INDEX_EXPIRY_SECS in configuration.md
- Add comprehensive rejected events metrics section to monitoring.md with Grafana queries and alerts
- Explain negentropy integration with rejected index in grasp-02-proactive-sync.md
- Document state event authorization defense-in-depth and rejection tracking in inline-authorization.md
This integrates information from work/rejected-events-index-summary.md into the main documentation,
ensuring architecture docs accurately reflect the implemented rejected events index system.
refactor(sync): rename ConnectedDegraded to ConnectedHistoricSyncFailures2026-01-09T14:23:44+00:00DanConwayDevDanConwayDev@protonmail.com2026-01-09T14:23:44+00:00urn:sha1:208ea60836cfc98857cf3359a73d8874ed5d935a
Resolves naming conflict with RelayHealthState::Degraded by using a more
explicit name that clearly indicates the connection status relates to
historic sync failures, not connection health degradation.
Changes:
- ConnectionStatus::ConnectedDegraded → ConnectedHistoricSyncFailures
- Updated all documentation and comments
- Updated Prometheus metric descriptions
- Metric value remains 4 for backward compatibility
This makes it clear that:
- ConnectedHistoricSyncFailures = connection lifecycle (missing historic data)
- RelayHealthState::Degraded = connection health (reliability issues)
These are orthogonal concerns - a relay can be ConnectedHistoricSyncFailures
but Healthy, or Connected but Degraded.
feat(sync): add ConnectedDegraded status for failed historic sync2026-01-09T14:12:24+00:00DanConwayDevDanConwayDev@protonmail.com2026-01-09T14:12:24+00:00urn:sha1:93a1684f068603b354ba3c05957a25459c73de05
- Add ConnectionStatus::ConnectedDegraded (status=4 in metrics)
- Track batch failures via PendingBatch.failed field
- Track relay-level failures via RelayState.historic_sync_had_failures
- Transition to ConnectedDegraded when any batch fails during historic sync
- Add is_live_sync_active() helper for cleaner match patterns
- Update state machine diagram with ConnectedDegraded transitions
- Update metrics docs with status=4 and example queries
Fixes issue where relays with failed negentropy retries would
incorrectly transition to Connected status despite missing data.
Now operators can distinguish 'fully synced' vs 'degraded (partial data)'.
feat(sync): add Syncing connection status to track historic sync progress2026-01-09T13:28:11+00:00DanConwayDevDanConwayDev@protonmail.com2026-01-09T13:28:11+00:00urn:sha1:c34492069abacae67482af4c8356241958a524f7
- Add ConnectionStatus::Syncing state between Connecting and Connected
- Track historic_sync_completed and historic_sync_completed_at in RelayState
- Auto-detect sync completion via check_and_complete_historic_sync()
- Update metrics: ngit_sync_relay_connected now shows 0-3 (disconnected/connecting/syncing/connected)
- Update Prometheus metric documentation with new status values
- Add state machine diagram showing Syncing transition
- Operators can now distinguish 'connected but catching up' vs 'fully synced'
docs: update GRASP-02 proactive sync event sync approach2025-12-04T16:54:38+00:00DanConwayDevDanConwayDev@protonmail.com2025-12-04T16:54:38+00:00urn:sha1:fdbc8895e1e9e712882bd854908295a95e7afcb9add prometheus metrics2025-12-04T15:24:19+00:00DanConwayDevDanConwayDev@protonmail.com2025-12-04T15:17:04+00:00urn:sha1:fd0c87c787d0626b3546fa571541c9c809711821