Repository navigation
feat: event monitoring setup wizard, omnichannel notifications, and poller improvements - #38
Merged
Merged
Conversation
- Add migration 011: trigger_source column on alerts, alert_notifications table
- Record trigger_source ('poller'/'event_consumer') on every alert
- Track per-channel delivery (slack, sns) in alert_notifications with delivered/failed status
- Make slack _post() return bool; propagate through post_investigation/post_failed_investigation
- notify_slack() returns bool for accurate delivery tracking
- Add /api/integrations router with POST /slack/test endpoint
- Integrations tab: Slack card with configured status + test button; GitHub/PagerDuty/Datadog/Telegram as coming soon
- AlertDetailPage: trigger source badge + notified-via section with per-channel status
- Fix Vite proxy missing /api/integrations entry
- Poller: fix failed investigations sending no Slack notification by calling post_failed_investigation directly when status is 'failed' (matches event consumer) - Poller: use poll interval as Lambda error rate window so only errors since last tick trigger new investigations (prevents stale alerts re-firing) - Poller/event consumer: add debug logs for alarm counts, Lambda counts, investigation start (with truncated session id) and completion with confidence - Init wizard: add skip disclaimers to steps 2 and 4 (amber warning + monitoring.md link + "Go to dashboard anyway" confirmation) so users understand what they're skipping - Init wizard: add back buttons to steps 3 and 4 so users can revise earlier answers
…alignment - App.tsx: guard init skip only for logged-in non-admin users (null user was bypassing the wizard on empty DB) - InitPage: fix Re-check button alignment in step 3 — drop flex-1, use justify-between so Back and Re-check sit at opposite ends
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
alert_notificationstable tracks per-channel delivery (Slack, SNS) withdelivered/failedstatus;trigger_sourcecolumn on alerts distinguishes poller vs event consumer; surfaced in AlertDetailPage as triggered-by badge and "Notified via" section.envhint, and "Send test message" button; GitHub/PagerDuty/Datadog/Telegram flagged as Coming Soonpost_failed_investigation(matches event consumer); Lambda error rate window uses poll interval instead of hardcoded 1 hour to prevent stale alerts re-firing; added debug logs for tick activityTest plan
/→ redirected to/initwizardfailedin notifications