Managing uptime-kuma effectively is a crucial skill for any system administrator. This tutorial provides step-by-step instructions for monitoring configuration, along with best practices for production environments.
Prerequisites
- A VPS running Ubuntu 22.04 or later (2GB+ RAM recommended)
- An active Kazepute VPS instance
- Root or sudo access to the server
- A registered domain name (for public-facing services)
Accessing the Marketplace
The default configuration works well for development environments, but production servers require additional tuning. Pay particular attention to connection limits, timeout values, and logging settings.
# Check marketplace app status
curl -s http://localhost:8080/health | jq .
# View application logs
docker logs -f uptime-kuma-app --since 1h
# Restart the marketplace app
docker compose -f /opt/uptime-kuma/docker-compose.yml restart
The output should show the service running without errors. If you see any warning messages, address them before proceeding to the next step.
- Test your backup restore procedure monthly
- Monitor disk space usage and set up alerts
- Keep your system packages updated regularly
- Review log files weekly for anomalies
- Enable automatic security updates for critical patches
Deployment Configuration
When scaling this setup, consider vertical scaling (adding more RAM/CPU) first, as it's simpler to implement. Horizontal scaling adds complexity but may be necessary for high-traffic applications.
# Check marketplace app status
curl -s http://localhost:8080/health | jq .
# View application logs
docker logs -f uptime-kuma-app --since 1h
# Restart the marketplace app
docker compose -f /opt/uptime-kuma/docker-compose.yml restart
These commands should be run as root or with sudo privileges. If you're using a non-root user, prefix each command with sudo.
- Use strong, unique passwords for all services
- Enable firewall and allow only necessary ports
- Use SSH keys instead of password authentication
- Set up fail2ban for brute force protection
- Keep all software components up to date
Post-Installation Setup
The default configuration works well for development environments, but production servers require additional tuning. Pay particular attention to connection limits, timeout values, and logging settings.
# Check marketplace app status
curl -s http://localhost:8080/health | jq .
# View application logs
docker logs -f uptime-kuma-app --since 1h
# Restart the marketplace app
docker compose -f /opt/uptime-kuma/docker-compose.yml restart
These commands should be run as root or with sudo privileges. If you're using a non-root user, prefix each command with sudo.
Configuration Options
For production deployments, consider implementing high availability by running multiple instances behind a load balancer. This approach provides both redundancy and improved performance under heavy load.
Managing the Application
For production deployments, consider implementing high availability by running multiple instances behind a load balancer. This approach provides both redundancy and improved performance under heavy load.
Advanced Settings
For production deployments, consider implementing high availability by running multiple instances behind a load balancer. This approach provides both redundancy and improved performance under heavy load.
- Use connection pooling for database connections
- Profile before optimizing - measure first
- Implement caching at every appropriate layer
Summary
You've successfully configured uptime-kuma on your VPS. Remember to monitor performance, keep your software updated, and maintain regular backups. If you run into issues, consult the official documentation or open a support ticket for assistance.