Uptime Kotlin: self-hosted uptime monitoring with status pages and an optional worker cluster mode

Hi r/selfhosted, I'm the author of Uptime Kotlin, an open-source (MIT) self-hosted uptime monitoring tool. I wanted a monitor with more precise checks and no single point of failure for the monitoring itself, so I built one where the checks can be spread across several workers. It has been developed in the open for 10 months, with versioned releases (currently v1.2.2), Docker images on GHCR, and an install guide in the README. What it does - Monitors HTTP/HTTPS, TCP, DNS, ping, PostgreSQL, SQL Server, MySQL/MariaDB, Redis, SMTP, Kafka and RabbitMQ - Real-time dashboard with historical data - Public status pages - Notifications via Email, Slack, Discord, Teams and Webhook, with optional periodic resend while a monitor stays down - Maintenance windows, per-probe log retention and configurable timeouts - Optional cluster mode: checks can be moved to one or more workers, coordinated through a job queue stored in PostgreSQL (no Redis or RabbitMQ needed) Stack Kotlin + Quarkus backend, React frontend, PostgreSQL, Docker Compose. Getting started The README has a Docker Compose setup, an environment variable reference, and update/backup instructions. You need to generate JWT keys and an encryption key before the first start. Known limitations - Notifications: Email, Slack, Discord, Teams and Webhook for now (no Telegram/ntfy/Gotify yet) - PostgreSQL is the only supported database - Workers are redundant, but the API and PostgreSQL are single instances in the default setup - No public demo instance What I'd like feedback on - Did the installation work on your first try? If not, where did it break? - Which monitor types or notification channels are missing for your setup? - Anything unclear in the documentation? GitHub: github.com/TheoMeunier/uptime-kotlin Website: uptime-kotlin.com I'll answer every comment. Thanks for reading!

添加评论
点赞收藏
点踩分享查看原文
评论
?
参与讨论