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.
Duration 7 hours
Course Outline
Achieving Monitoring Sovereignty for Teams
- Understanding how cloud monitoring SaaS can expose infrastructure topology and performance data.
- Overview of Uptime Kuma’s architecture: Node.js, SQLite, and Vue.js frontend.
- Comparative analysis with Nagios, Zabbix, and Grafana OnCall.
Rapid Deployment
- Installing via a single Docker command and managing volume persistence.
- Configuring reverse proxies and TLS.
- Performing initial setup and creating an admin account.
- Setting environment variables for authentication and base URL.
Types of Monitors
- HTTP/HTTPS monitoring with keyword and status code validation.
- Monitoring TCP ports and ping/ICMP responses.
- DNS resolution and specific query-type checks.
- Using push monitors for cron job and backup heartbeats.
- Monitoring MQTT, gRPC, and game servers.
Alerting Mechanisms
- Configuring SMTP email and Microsoft Teams webhooks.
- Setting up bots for Slack, Discord, Telegram, and Signal.
- Integrating with PagerDuty, Opsgenie, and custom webhook payloads.
- Implementing notification throttling and escalation policies.
Status Pages
- Creating branded public status pages.
- Managing incident timelines and maintenance modes.
- Applying custom CSS and mapping domains.
- Generating RSS and JSON feeds for status automation.
Integration and Maintenance
- Utilizing the Prometheus metrics endpoint for external scraping.
- Using the API for bulk creation and management of monitors.
- Performing database backups and migrations.
- Updating and securing the instance.
Requirements
- Foundational knowledge of Linux and Docker administration.
- Working understanding of HTTP, TCP, and core monitoring concepts.
- Experience with common notification channels such as email, Slack, and Discord.
Target Audience
- SREs and DevOps teams seeking to replace cloud-based monitoring dashboards.
- Small teams requiring simple, sovereign uptime monitoring solutions.
- Organizations avoiding SaaS monitoring tools for compliance reasons.
