OneUptime — Complete Open-Source Monitoring and Incident Management Platform

Introduction

OneUptime combines uptime monitoring, status pages, incident management, on-call rotation, and log management into a single self-hosted platform. It aims to replace the combination of Pingdom, PagerDuty, and StatusPage with one unified open-source tool.

What OneUptime Does

• Monitors websites, APIs, servers, and containers with configurable health checks
• Hosts public and private status pages with real-time incident updates
• Routes alerts through on-call schedules with escalation policies
• Manages incident lifecycle from detection through resolution and postmortem
• Collects logs and traces for correlation with monitoring alerts

Architecture Overview

OneUptime runs as a set of microservices orchestrated via Docker Compose or Kubernetes. A probe service executes health checks from configurable global locations. Results flow into a PostgreSQL database and trigger the alerting pipeline, which evaluates on-call schedules and sends notifications via email, SMS, Slack, or webhooks. The React frontend provides dashboards, status page configuration, and incident management workflows.

Self-Hosting & Configuration

• Deploy with Docker Compose for small teams or Helm chart for Kubernetes clusters
• Configure monitoring probes in multiple regions for global coverage
• Set up SMTP, Twilio, and Slack integrations for multi-channel alerting
• Customize status page branding with your domain, logo, and color scheme
• Enable SSO via SAML or OpenID Connect for enterprise authentication

Key Features

• All-in-one platform eliminates tool sprawl and data silos across monitoring stacks
• On-call scheduling with rotation, escalation, and acknowledgment tracking
• Probe-based monitoring supports HTTP, TCP, UDP, ping, and custom scripts
• Status pages are fully customizable and support scheduled maintenance windows
• Built-in workflow automation triggers actions based on incident state changes

Comparison with Similar Tools

• Datadog — comprehensive but expensive SaaS; OneUptime is self-hosted and free
• PagerDuty — focused on incident routing; OneUptime adds monitoring and status pages
• Uptime Kuma — simpler uptime monitor; OneUptime includes full incident lifecycle
• Grafana OnCall — on-call only; OneUptime bundles monitoring and status pages
• Statuspage (Atlassian) — status pages only; OneUptime is the complete stack

FAQ

Q: Can OneUptime replace both my monitoring and incident tools? A: Yes. It covers uptime monitoring, alerting, on-call scheduling, incident management, and public status pages in one platform.

Q: How does probe-based monitoring work for global coverage? A: You deploy probe containers in different regions. Each probe independently checks your endpoints and reports back to the central server for correlated alerting.

Q: Is there a limit on the number of monitors or team members? A: No. The open-source version has no artificial limits on monitors, users, or incidents.

Q: Can I migrate from existing tools like PagerDuty or Pingdom? A: OneUptime provides API endpoints for bulk configuration. Community scripts exist for importing monitors and on-call schedules from common platforms.

Sources

• https://github.com/OneUptime/oneuptime
• https://oneuptime.com/docs