Thank you for sending your enquiry! One of our team members will contact you shortly.
Thank you for sending your booking! One of our team members will contact you shortly.
Course Outline
Monitoring Sovereignty for Teams
- Understanding the risks of cloud monitoring SaaS regarding infrastructure topology and performance data exposure.
- Overview of Uptime Kuma architecture: Node.js, SQLite, and Vue.js frontend.
- Comparison with Nagios, Zabbix, and Grafana OnCall.
Quick Deployment
- Docker one-liner installation and volume persistence setup.
- Reverse proxy and TLS configuration.
- Initial setup and admin account creation.
- Configuring environment variables for authentication and base URL.
Monitor Types
- HTTP/HTTPS monitoring with keyword and status code checks.
- TCP port and ping/ICMP monitoring.
- DNS resolution and query-type checks.
- Push monitors for cron jobs and backup heartbeats.
- Monitoring for MQTT, gRPC, and game servers.
Alerting Channels
- SMTP email and Microsoft Teams webhooks.
- Integration with Slack, Discord, Telegram, and Signal bots.
- PagerDuty, Opsgenie, and custom webhook payloads.
- Notification throttling and escalation policies.
Status Pages
- Creating branded public status pages.
- Managing incident timelines and maintenance modes.
- Applying custom CSS and domain mapping.
- Utilizing RSS and JSON feeds for status automation.
Integration and Maintenance
- Exposing Prometheus metrics endpoints for external scraping.
- Using the API for bulk monitor creation and management.
- Performing database backup and migration procedures.
- Updating and securing the Uptime Kuma instance.
Requirements
- Fundamental knowledge of Linux and Docker administration.
- Understanding of HTTP, TCP protocols, and monitoring concepts.
- Familiarity with notification channels such as email, Slack, and Discord.
Audience
- SREs and DevOps teams seeking to replace cloud monitoring dashboards.
- Small teams requiring simple, sovereign uptime monitoring solutions.
- Organizations avoiding SaaS monitoring tools for compliance reasons.
7 Hours