MrSphay/intelligence-terminal
1
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases Wiki Activity

Send operator alerts when dashboard data remains stale #2

New Issue
Closed
opened 2026-05-17 11:21:48 +00:00 by MrSphay · 2 comments
MrSphay commented 2026-05-17 11:21:48 +00:00
Owner
Copy Link

Derived from upstream Crucix #108 and the production Docker stale-data incident: https://github.com/calesthio/Crucix/issues/108

Current status in this fork: /api/health now reports stale state and the dashboard fetches live /api/data, but Telegram/Discord do not proactively notify when repeated sweeps fail and data stays stale.

Acceptance criteria:

  • Trigger Telegram/Discord operator alerts when data age exceeds STALE_DATA_MAX_AGE_MINUTES after failed/degraded sweeps.
  • Deduplicate stale alerts so they do not spam every interval.
  • Include last successful sweep, last error, source failure summary, and dashboard URL guidance.
  • Add unit/integration coverage for stale threshold behavior.
Derived from upstream Crucix #108 and the production Docker stale-data incident: https://github.com/calesthio/Crucix/issues/108 Current status in this fork: /api/health now reports stale state and the dashboard fetches live /api/data, but Telegram/Discord do not proactively notify when repeated sweeps fail and data stays stale. Acceptance criteria: - Trigger Telegram/Discord operator alerts when data age exceeds STALE_DATA_MAX_AGE_MINUTES after failed/degraded sweeps. - Deduplicate stale alerts so they do not spam every interval. - Include last successful sweep, last error, source failure summary, and dashboard URL guidance. - Add unit/integration coverage for stale threshold behavior.
MrSphay commented 2026-05-17 11:54:25 +00:00
Author
Owner
Copy Link

In Bearbeitung durch Codex auf Branch codex/issue-2-stale-alerts. Scope: Operator-Alerts bei stale Daten nach fehlgeschlagenen/degradierten Sweeps, Deduping gegen Alert-Spam, Tests/Doku. �nderungen werden auf Server/Alerts/Tests/Doku begrenzt, damit Issue #1 und UI-Arbeiten separat mergbar bleiben.

In Bearbeitung durch Codex auf Branch codex/issue-2-stale-alerts. Scope: Operator-Alerts bei stale Daten nach fehlgeschlagenen/degradierten Sweeps, Deduping gegen Alert-Spam, Tests/Doku. �nderungen werden auf Server/Alerts/Tests/Doku begrenzt, damit Issue #1 und UI-Arbeiten separat mergbar bleiben.
MrSphay commented 2026-05-17 11:59:22 +00:00
Author
Owner
Copy Link

Implementierung gepusht und PR ge�ffnet: #12

Branch: codex/issue-2-stale-alerts
Commit: e574ad1
Status: lokale Checks gr�n; �nderungen sind bewusst von Issue #1 getrennt und package.json wurde nicht ver�ndert, um Merge-Konflikte mit PR #9 zu vermeiden.

Implementierung gepusht und PR ge�ffnet: https://git.wilkensxl.de/MrSphay/intelligence-terminal/pulls/12 Branch: codex/issue-2-stale-alerts Commit: e574ad1 Status: lokale Checks gr�n; �nderungen sind bewusst von Issue #1 getrennt und package.json wurde nicht ver�ndert, um Merge-Konflikte mit PR #9 zu vermeiden.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
design-revert
Reverts visual/design changes
 enhancement
New feature or product improvement
 frontend-redesign
Frontend redesign and app-shell/UI work
 marketing-finalization
Product presentation, README, packaging metadata, and customer-facing communication.
 product
User-facing product capability or workflow
 research
Research-originated product idea ready for implementation design
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
MrSphay
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MrSphay/intelligence-terminal#2
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?