🎯 Bounty: Uptime Monitoring Alarm Integration

[izadoesdev]

🎯 Bounty: Uptime Monitoring Alarm Integration

Bounty: $15

Depends on: #267 (Alarms System)

Overview

Integrate the alarms system with uptime monitoring to trigger notifications when a site goes down or comes back up. Users should be able to assign alarms to their monitored websites and receive notifications via their configured channels (Slack, Discord, Email, Webhook).

Requirements

1. Uptime Trigger Integration (Required)

Connect the uptime monitoring service to the alarms system.

Trigger Events:

• Site goes down (consecutive failures threshold met)
• Site comes back up (recovery)
• Response time exceeds threshold (optional/stretch)

Acceptance Criteria:

• Uptime service checks for alarms assigned to the website
• Triggers alarm when site status changes (up → down, down → up)
• Respects configurable thresholds (e.g., alert after X consecutive failures)
• Prevents duplicate notifications (don't spam on every check)
• Logs alarm trigger history

2. Alarm Assignment UI (Required)

Allow users to assign alarms to monitored websites.

UI Requirements:

• Uptime monitoring page shows assigned alarms
• Quick-assign dropdown to add existing alarms
• Option to create new alarm directly from uptime page
• Visual indicator showing which alarms are active

Acceptance Criteria:

• Alarm assignment UI in uptime monitoring section
• Matches existing dashboard design patterns
• Mobile responsive
• Uses existing UI components

3. Notification Content (Required)

Send rich, informative notifications when alarms trigger.

Down Notification Content:

• Website URL
• Time detected
• HTTP status code (if available)
• Response time (if available)
• Number of consecutive failures
• Link to uptime dashboard

Up Notification Content:

• Website URL
• Time recovered
• Downtime duration
• Link to uptime dashboard

Acceptance Criteria:

• Uses @databuddy/notifications package helpers
• Notifications include all relevant site details
• Channel-specific formatting (Slack blocks, Discord embeds, HTML email)
• Professional, clean design matching Databuddy branding

4. Testing (Required)

Acceptance Criteria:

• Unit tests for alarm trigger logic
• Test threshold behavior (only trigger after X failures)
• Test duplicate prevention (no spam)
• Test both down and up notifications
• Test multi-channel delivery

Technical Requirements

• Follow existing codebase patterns in apps/uptime/
• Use @databuddy/notifications package for sending notifications
• TypeScript with strict types (no any, unknown, or never)
• Use dayjs for time calculations and formatting
• Proper error handling (don't crash uptime service on notification failure)

Files to Reference

• apps/uptime/src/ - Uptime monitoring service
• packages/notifications/ - Notification providers and helpers
• packages/db/src/drizzle/schema.ts - Database schema (alarms table from 🎯 Bounty: Alarms System - Database, API & Dashboard UI #267)
• apps/dashboard/app/(main)/websites/[id]/uptime/ - Uptime dashboard UI

Example Usage

import { sendSlackWebhook, sendDiscordWebhook } from "@databuddy/notifications";

// When site goes down
await sendSlackWebhook(alarm.slack_webhook_url, {
  title: "🔴 Site Down: example.com",
  message: "Your website is not responding.",
  priority: "urgent",
  metadata: {
    url: "https://example.com",
    status: 503,
    downSince: "2 minutes ago",
    consecutiveFailures: 3,
  },
});

// When site recovers
await sendDiscordWebhook(alarm.discord_webhook_url, {
  title: "🟢 Site Recovered: example.com",
  message: "Your website is back online.",
  priority: "normal",
  metadata: {
    url: "https://example.com",
    downtimeDuration: "5 minutes",
    recoveredAt: new Date().toISOString(),
  },
});

Submission Requirements

• All code follows linting rules (run bun run lint)
• Type checks pass (run bun run check-types)
• Tests pass
• PR includes screenshots of notification examples
• PR description explains implementation choices

Questions?

Comment on this issue for any clarification needed before starting.

[izadoesdev]

/bounty 15

[algora-pbc]

💎 $15 bounty • Jacques Anidjar

💎 $15 bounty • Databuddy

Steps to solve:

1. Start working: Comment /attempt #268 with your implementation plan
2. Submit work: Create a pull request including /claim #268 in the PR body to claim the bounty
3. Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts

❗ Important guidelines:

• To claim a bounty, you need to provide a short demo video of your changes in your pull request
• If anything is unclear, ask for clarification before starting as this will help avoid potential rework
• Low quality AI PRs will not receive review and will be closed
• Do not ask to be assigned unless you've contributed before

Thank you for contributing to databuddy-analytics/Databuddy!

Attempt	Started (UTC)	Solution	Actions
🟢 @jacanidjar	Jan 16, 2026, 12:54:55 PM	#278	Reward
🟢 @Aidenzx	Jan 16, 2026, 02:51:38 PM	WIP
🟢 @bikramadhikari001	Jan 20, 2026, 03:53:23 AM	WIP

[izadoesdev]

NOTE: this was mostly written by AI, so if anything is sub-optimal, can be changed, feel free to do so, this is in no way the final PRD, but it does convey the final result, how you create it is up to you

[jacanidjar]

/attempt #268

[Aidenzx]

/attempt #268