How phiraphat29/uptime-monitor works
This is a full-stack uptime monitor: users manage monitored URLs in a Next.js dashboard; the Go API stores monitor configuration, while a background worker checks targets, records results, and sends Discord alerts on state changes. Dashboard views include recent uptime history and latency charts, plus a controllable mock target for demonstrations. The README documents UI capabilities and API routes; source excerpts show the main calls and persistence/checking behavior. Some component-level frontend wiring is documented rather than shown in excerpts.
Main entry points: monitor_handler.go Monitor Handlers · checker.go Health Checker · page.tsx Dashboard · database.go Database Connection
Components 17
Dashboard
- Dashboard
frontend/src/app/page.tsx - Monitor Form
frontend/src/components/AddMonitorModal.tsx - Monitor Card
frontend/src/components/MonitorCard.tsx - Uptime Bar
frontend/src/components/UptimeBar.tsx - Latency Chart
frontend/src/components/LatencyChart.tsx - Demo Controls
frontend/src/components/Navbar.tsx - API Client
frontend/src/lib/api.ts
Backend API
- HTTP Server
backend/main.go - Monitor Handlers
backend/handlers/monitor_handler.go - Mock Target
backend/handlers/monitor_handler.go
Monitoring
- Health Checker
backend/worker/checker.go
Persistence
- Database Connection
backend/config/database.go - Monitor Records
backend/models/monitor.go
Other components
- Operator
- Monitored Target
- Discord Webhook
- PostgreSQL
Connections 23
- Operator → Dashboard: uses
README.md - Dashboard → API Client: requests data
frontend/src/app/page.tsx - Dashboard → Monitor Form: opens
frontend/src/app/page.tsx - Dashboard → Monitor Card: renders
frontend/src/app/page.tsx - Monitor Card → Uptime Bar: shows history
README.md - Monitor Card → Latency Chart: shows latency
README.md - Dashboard → Demo Controls: offers controls
README.md - Monitor Form → API Client: tests webhook
frontend/src/components/AddMonitorModal.tsx - API Client → Monitor Handlers: calls REST API
frontend/src/lib/api.ts - HTTP Server → Monitor Handlers: routes requests
backend/main.go - HTTP Server → Database Connection: connects database
backend/main.go - HTTP Server → Health Checker: starts worker
backend/main.go - Monitor Handlers → Database Connection: reads and writes
backend/handlers/monitor_handler.go - Monitor Handlers → Monitor Records: uses records
backend/handlers/monitor_handler.go - Monitor Handlers → Health Checker: starts checks
backend/handlers/monitor_handler.go - Monitor Handlers → Mock Target: serves demo
backend/handlers/monitor_handler.go - Health Checker → Database Connection: queries and saves
backend/worker/checker.go - Health Checker → Monitor Records: records results
backend/worker/checker.go - Health Checker → Monitored Target: checks URL
backend/worker/checker.go - Health Checker → Discord Webhook: sends alerts
backend/worker/checker.go - Database Connection → Monitor Records: migrates schema
backend/config/database.go - Database Connection → PostgreSQL: connects
backend/config/database.go - Monitored Target → Mock Target: demo endpoint