How vitaliandrushkevich/pulse works
Pulse is a self-hosted uptime-monitoring platform: users configure monitors and notification rules through the web UI or REST API, then inspect live status, history, incidents, and alerts. The scheduler dispatches bounded checks to protocol-specific workers; results feed time-series storage and the WebSocket hub, while notification dispatch evaluates state changes and delivers alerts. The MCP server provides a separate AI-assistant entry point to the Pulse API. Unsampled feature links reflect README documentation; source-specific links cite excerpts or indexed references.
Main entry points: router.go HTTP router · monitor Protocol checkers · +page.svelte Dashboard · scheduler.go Check scheduler
Components 21
API and access
- HTTP router
backend/internal/api/router.go - REST handlers
backend/internal/api/handlers - Authentication
backend/internal/api/middleware/auth.go - Prometheus metrics
backend/internal/metrics/prometheus.go
Monitoring engine
- Check scheduler
backend/internal/monitor/scheduler.go - Protocol checkers
backend/internal/monitor - Target normalization
backend/internal/target/normalize.go
State and delivery
- PostgreSQL state
backend/internal/store/postgres - Time-series store
backend/internal/store/timescale/store.go - WebSocket hub
backend/internal/hub/hub.go - Alert dispatch
backend/internal/notification/dispatcher.go - Email and webhook
backend/internal/notification
Web application
- Embedded frontend
backend/internal/frontend/frontend.go - Dashboard
frontend/src/routes/+page.svelte - Monitor views
frontend/src/routes/monitors/[id]/+page.svelte - Dashboard insights
frontend/src/components/dashboard/InsightsPanel.svelte
MCP integration
- MCP server
mcp/internal/server/server.go - MCP tools
mcp/internal/tools - Pulse API client
mcp/internal/pulseapi/http_client.go
Other components
- Operator
- AI assistant
Connections 19
- Operator → HTTP router: uses API
- HTTP router → REST handlers: routes requests
backend/internal/api/router.go - HTTP router → Authentication: protects routes
backend/internal/api/router.go - HTTP router → Prometheus metrics: exposes metrics
backend/internal/api/router.go - HTTP router → Embedded frontend: serves assets
backend/internal/api/router.go - REST handlers → PostgreSQL state: reads and writes
- Check scheduler → Protocol checkers: dispatches checks
- Protocol checkers → Time-series store: persists results
- Protocol checkers → WebSocket hub: broadcasts results
- WebSocket hub → Dashboard: sends patches
- Dashboard → Dashboard insights: renders
frontend/src/routes/+page.svelte - Operator → Dashboard: views status
- Operator → Monitor views: manages monitors
- Alert dispatch → Email and webhook: delivers alerts
- Check scheduler → Alert dispatch: evaluates transitions
- AI assistant → MCP server: invokes tools
- MCP server → MCP tools: registers tools
mcp/internal/server/server.go - MCP tools → Pulse API client: calls API
mcp/internal/tools/create_monitor.go - Pulse API client → HTTP router: sends requests