Closed geerlingguy closed 9 years ago
So... munin-html
takes 100% CPU for about 20 seconds, then munin-graph
takes over and spikes to 100% for about 3 minutes. A little longer, and the graphing cycle will basically be continuous!
Configuring Munin to use FastCGI with Nginx is not the most complicated affair (mostly involves maybe 4-6 more tasks in a playbook on the balancer... plus a bit more config in the Nginx .conf
file...). This might be a deal-breaker, though, on the poor Pis.
I think we have four routes:
Another option worth exploring... Munin doesn't have a magic enabled
var in munin.conf (sadly), but I could add a munin_enabled
variable to the munin role, or a dramble_munin_enabled
role specific to this configuration that removes the cron job. See: https://github.com/geerlingguy/ansible-role-munin/issues/2
Done! Munin can now be toggled at-will by setting munin_cron_job
to present
or absent
.
It'd be nice to have a HUD of the entire cluster's activity. Munin is lightweight, easy to get going, and can maybe run on one of the three webservers, or on the caching server maybe...