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 how cloud monitoring SaaS can expose infrastructure topology and performance data.
- Exploring Uptime Kuma’s architecture: Node.js, SQLite, and the Vue.js frontend.
- Comparative analysis with Nagios, Zabbix, and Grafana OnCall.
Swift Deployment
- One-liner Docker installation and ensuring volume persistence.
- Setting up reverse proxies and TLS.
- Initial configuration and creating the admin account.
- Managing environment variables for authentication and base URL.
Monitor Types
- HTTP/HTTPS checks with keyword and status code validation.
- TCP port availability and ping/ICMP monitoring.
- DNS resolution and specific query-type checks.
- Push monitors for cron job and backup heartbeats.
- Monitoring for MQTT, gRPC, and game servers.
Alerting Channels
- SMTP email integration and Microsoft Teams webhooks.
- Bots for Slack, Discord, Telegram, and Signal.
- PagerDuty, Opsgenie, and custom webhook payloads.
- Implementing notification throttling and escalation policies.
Status Pages
- Building branded public status pages.
- Managing incident timelines and maintenance modes.
- Applying custom CSS and mapping domains.
- Utilizing RSS and JSON feeds for status automation.
Integration and Maintenance
- Prometheus metrics endpoints for external scraping.
- API usage for bulk monitor creation and management.
- Database backup and migration strategies.
- Updating and securing the Uptime Kuma instance.
Requirements
- Foundational knowledge of Linux and Docker administration.
- A solid grasp of HTTP, TCP, and core monitoring concepts.
- Experience with common notification channels such as email, Slack, and Discord.
Audience
- SREs and DevOps teams transitioning away from cloud monitoring dashboards.
- Small teams requiring simple, sovereign uptime monitoring solutions.
- Organizations seeking to avoid SaaS monitoring for compliance reasons.
7 Hours