Alarms system: DB schema, RPC endpoints, dashboard UI & uptime integration

[samuel-asleep]

Summary

This PR implements a complete alarms/notifications system for Databuddy, covering both #267 (Alarms System) and #268 (Uptime Monitoring Alarm Integration).
It provides end-to-end support for defining alarms, assigning them to websites, and triggering notifications based on uptime state changes, with coordinated backend processing and dashboard UI.

---

What’s included

Alarm / Notification System

• Added a new alarm management UI under Settings → Notifications
  (apps/dashboard/app/(main)/settings/notifications/page.tsx)
• Users can create, edit, test, enable/disable, and delete alarms
• Support for multiple notification channels
• Introduced a reusable alarms hook integrated with React Query and organization context

Website alarm assignment

• Added alarm assignment UI for websites, allowing alarms to be attached or removed per site
• Integrated into the website Pulse / Uptime pages
• Unified uptime and pulse logic to avoid duplication

Backend alarm processing

• Implemented uptime alarm evaluation and trigger handling
• Notification delivery and alarm state management handled in runtime logic
• Backend processing isolated in alarms-runtime.ts

Dependencies

• Added required notification and shared utilities to support alarm delivery and processing
• Reuses existing Databuddy notification infrastructure

---

Screenshots

Homepage (login/signup page)

Alarm shown on Notifications page

---

Testing

• Unit tests added for alarm RPC handlers and uptime alarm processing
• Manual verification performed via the dashboard UI in a dev environment

---

AI Disclosure

This PR was created with AI-assisted tooling in a strict human-in-the-loop workflow.

• Tools used: GitHub Copilot, OpenAI Codex
• Extent of AI use:
  • Used for code review assistance, refactor suggestions, and identifying potential issues
  • Used for brainstorming structure and edge cases
• Human verification:
  • All AI-suggested changes were manually reviewed and modified where necessary
  • Unit tests were written and executed locally
  • UI behavior was manually tested via the dashboard
• Scope compliance:
  • This PR strictly targets accepted issues 🎯 Bounty: Alarms System - Database, API & Dashboard UI #267 and 🎯 Bounty: Uptime Monitoring Alarm Integration #268
  • No AI-generated media (images, video, audio) was used

All final implementation decisions, validation, and testing were performed manually.

---

Notes

• This PR targets the dashboard and uptime codepaths where alarms and monitoring logic currently live
• Scope is limited strictly to the requirements of 🎯 Bounty: Alarms System - Database, API & Dashboard UI #267 and 🎯 Bounty: Uptime Monitoring Alarm Integration #268

---

Claims

/claim #268
/claim #267

---

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (where applicable)
• My changes generate no new warnings (aside from known environment-related font warnings)
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[CLAassistant]

All committers have signed the CLA.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

• 🔍 Trigger a full review

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[vercel]

@samuel-asleep is attempting to deploy a commit to the Databuddy OSS Team on Vercel.

A member of the Team first needs to authorize it.

[dosubot]

Related Documentation

Checked 1 published document(s) in 1 knowledge base(s). No updates required.

^{How did I do? Any feedback?}  

[greptile-apps]

Greptile Overview

Greptile Summary

This PR implements a comprehensive alarm and notification system for Databuddy, integrating uptime monitoring with multi-channel alerts. The implementation includes database schema with three tables (alarms, alarm_state, alarm_trigger_history), backend processing logic with threshold-based state evaluation, RPC endpoints for alarm management, and a polished dashboard UI.

Key Changes

• Database schema: Composite primary key (alarmId, websiteId) in alarm_state correctly supports multiple website assignments per alarm
• Alarm processing: Threshold-based failure detection with consecutive failure tracking before triggering notifications
• Multi-channel notifications: Support for Slack, Discord, Email, and custom webhooks with proper error handling
• State management: Tracks alarm state transitions (up/down) and prevents duplicate notifications
• UI components: Full CRUD interface in Settings → Notifications plus website-specific alarm assignment in Pulse/Uptime pages
• Test coverage: Unit tests for alarm logic, state evaluation, and RPC handlers

Architecture

The alarm system follows a clean separation of concerns:

1. Configuration layer (RPC + UI) for managing alarms
2. Runtime processor that evaluates uptime data against alarm conditions
3. Notification dispatcher supporting multiple channels
4. State tracking to prevent notification spam

The implementation correctly addresses the previous schema concerns by using composite keys and proper conflict resolution in upserts.

Confidence Score: 5/5

• Safe to merge - well-tested feature with proper error handling and no breaking changes
• The implementation is complete, well-structured, and addresses previous schema concerns. Composite primary keys are correctly used, tests cover critical paths, error handling is comprehensive, and the code follows the project's patterns.
• No files require special attention

Important Files Changed

Filename	Overview
packages/db/src/drizzle/schema.ts	Added three alarm tables with proper composite primary key for alarm_state, foreign key relationships, and indexes
packages/db/src/drizzle/0001_alarms.sql	SQL migration creates alarm tables with composite primary key and proper cascading constraints
apps/uptime/src/alarms.ts	Core alarm logic with state evaluation, notification building, and multi-channel sending
apps/uptime/src/alarms-runtime.ts	Database integration layer that connects alarm processing to Drizzle ORM with composite key handling
apps/uptime/src/index.ts	Integrated alarm processing into uptime check flow with error handling
packages/rpc/src/routers/alarms.ts	RPC endpoints for CRUD operations with user-scoped authorization and input validation
apps/dashboard/components/alarms/alarm-dialog.tsx	Alarm form dialog with channel-specific validation and dynamic field rendering

Sequence Diagram

sequenceDiagram
    participant User
    participant Dashboard
    participant RPC
    participant DB
    participant Uptime
    participant Alarms
    participant Notify

    Note over User,Dashboard: Alarm Configuration
    User->>Dashboard: Create/Edit Alarm
    Dashboard->>RPC: alarms.create/update
    RPC->>DB: Insert/Update alarms table
    DB-->>RPC: Alarm record
    RPC-->>Dashboard: Success
    Dashboard->>RPC: Assign alarm to website
    RPC->>DB: Update alarm.websiteId
    DB-->>Dashboard: Alarm assigned

    Note over Uptime,Notify: Uptime Monitoring & Alarm Processing
    Uptime->>Uptime: Execute scheduled check
    Uptime->>DB: Query uptime_schedules
    DB-->>Uptime: Schedule data
    Uptime->>Uptime: Perform HTTP check
    Uptime->>Alarms: processUptimeAlarms(uptimeData, websiteId)
    Alarms->>DB: Fetch enabled alarms for website
    DB-->>Alarms: Active alarms list
    Alarms->>DB: Fetch alarm_state for alarms
    DB-->>Alarms: Previous state records
    Alarms->>Alarms: evaluateAlarmState(previous, isDown, threshold)
    alt Threshold reached (first down notification)
        Alarms->>DB: Upsert alarm_state (status=down)
        Alarms->>Notify: sendNotifications(alarm, downPayload)
        Notify->>Notify: Send via Slack/Discord/Email/Webhook
        Notify-->>Alarms: Results
        Alarms->>DB: Insert alarm_trigger_history
    else Site recovered (up notification)
        Alarms->>DB: Upsert alarm_state (status=up, reset counters)
        Alarms->>Notify: sendNotifications(alarm, upPayload)
        Notify->>Notify: Send via configured channels
        Notify-->>Alarms: Results
        Alarms->>DB: Insert alarm_trigger_history
    else Still down but not notifying
        Alarms->>DB: Upsert alarm_state (increment failures)
    end
    Alarms-->>Uptime: Processing complete
    Uptime->>DB: Store uptime result

Loading

[greptile-apps]

_{5 files reviewed, 4 comments}

_{Edit Code Review Agent Settings | Greptile}

[samuel-asleep]

@izadoesdev can you please review my pr

[izadoesdev]

@greptile review

[izadoesdev]

I'm gonna go ahead and assume this is slop-coded since there's a few critical issues (as mentioned by Greptile) and you haven't disclosed it which violates our AI Usage policy, which is a first strike

Also, you provided a screenshot of the login page rather than the actual changes made??? I don't understand what you expect me to do with this review

[samuel-asleep]

@izadoesdev Thanks for pointing this out — that’s on me.

I should have clearly disclosed AI assistance up front, and I’ll update the PR description immediately to fully comply with the AI usage policy.

I’ll also replace the screenshot with concrete diffs / screenshots of the actual changes so the review is actionable.

Sorry for the confusion here — I’ll fix these items now so the PR can be reviewed properly.

[samuel-asleep]

@izadoesdev I’ve updated the PR description to include an explicit AI usage disclosure and added screenshots that directly show the implemented alarms UI on the Notifications page.

Please let me know if you’d like me to adjust anything further or add more reviewable context.

[samuel-asleep]

@izadoesdev can you please review my pr

[samuel-asleep]

@izadoesdev is there any more changes you need me to make ?

[samuel-asleep]

@izadoesdev ?

[izadoesdev]

This looks very vibe-coded and low quality, the design does not at all match our designs / other pages, it uses database migrations despite us not using them beforehand, it just does not match the quality we're looking for