Uptime Kuma
Uptime Kuma is a fancy, self-hosted monitoring tool with a beautiful reactive dashboard and status pages. It supports monitoring via HTTP(s), TCP, DNS, ICMP Ping, gRPC, Docker containers, Steam game servers, MQTT, and more. This stack deploys Uptime Kuma with persistent SQLite storage for all monitoring data and configuration. It provides multiple notification channels including Telegram, Discord, Slack, email (SMTP), Pushover, Gotify, Matrix, Teams, and 90+ other integrations. Features include customizable status pages, maintenance windows, badge generation for README files, multi-language support, and two-factor authentication. After deployment, access the web UI on port 3001 to create your admin account and start adding monitors for your services.
Servicios Incluidos
uptime-kuma
louislam/uptime-kuma:1
Variables de Entorno:
YAML Generado
# Generated by ComposeHub (composehub.dev)
name: uptime-kuma
services:
uptime-kuma:
image: louislam/uptime-kuma:1
restart: always
ports:
- 3001:3001
volumes:
- uptimekuma_data:/app/data
environment:
UPTIME_KUMA_PORT: ${UPTIME_KUMA_PORT:-3001}
UPTIME_KUMA_HOST: ${UPTIME_KUMA_HOST:-0.0.0.0}
networks:
- uptime-kuma
healthcheck:
test:
- CMD-SHELL
- >-
node -e "const http = require('http'); const options = { hostname: 'localhost', port: 3001, path:
'/api/health', timeout: 5000 }; http.get(options, (res) => { process.exit(res.statusCode === 200 ? 0 : 1)
}).on('error', () => { process.exit(1) })"
interval: 30s
timeout: 10s
retries: 3
start_period: 30s
deploy:
resources:
limits:
cpus: "1.00"
memory: 512M
reservations:
cpus: "0.10"
memory: 64M
labels:
com.composehub.description: Uptime Kuma monitoring dashboard and status page
networks:
uptime-kuma:
driver: bridge
volumes:
uptimekuma_data:
driver: local
Información Rápida
- Servicios
- 1
- Redes
- 1
- Volúmenes
- 1
Cuándo Usar
Esta plantilla es ideal para configurar un entorno de uptime kuma Todos los servicios vienen preconfigurados con healthchecks, límites de recursos y valores por defecto sensatos. Personaliza las variables de entorno antes de desplegar en producción.
Consejos
- Cambia todas las contraseñas por defecto antes de desplegar
- Revisa los límites de recursos para tu hardware
- Añade un proxy inverso para HTTPS en producción
- Configura estrategias de respaldo para los volúmenes de datos