Case study: How we brought order to our Matomo Saas with DevOps
summary
Claims a repeatable path from messy multi-tenant Matomo instances to a maintainable SaaS: use Rancher control plane for cluster visibility, add Neuvector for risk scanning, run Prometheus/Loki/Grafana alerts, and deploy via ArgoCD with a homemade Rust config generator; nightly cron exports push one file per day into ClickHouse and Superset as RebelMetrics on ClickHouse for advanced reports; rollbacks work, resource use drops, and team stress falls — mental health rises ~100%.
AI-written summary · about
chapters (9)
- 0:00From oceanography to DevOps
- 2:05Chaos to mature Matomo SaaS
- 4:16Scaling Matomo challenges
- 6:03Rust and Rancher automation
- 9:56Monitoring and alerts
- 12:05CI/CD future plans
- 12:47Introducing Matomo
- 14:32Rebel Metrics analytics
- 19:23Q&A
related talks
14mFrom the Ranch(er) to the Dev: A Case Study About Simplifying K8s Cluster Setup Wit...
13mLightning Talk: Observability-First DevSecOps: Building Resilient Multi-Cloud P...
27mA Safari of Kubernetes and its Natural Habitat
27mMonitoring as Code: Managing your Observability Assets the Cloud-Native Way
48mMetrics All the Way: Data Driven Operations
36mCyscale's Journey on Kubernetes
16mRevolutionizing Healthcare Data Processing with Kubernetes
42mRevolutionize Your Deployment Pipeline