Seems that Canonical's landscape is pretty good for that, but canonical's support said that payment plans starts from 100 servers =/
If you have 5+ servers – does you use anything to monitor and update all of them? If use – what is it?
1–10 of 15 posts
Seems that Canonical's landscape is pretty good for that, but canonical's support said that payment plans starts from 100 servers =/
If you have 5+ servers – does you use anything to monitor and update all of them? If use – what is it?
Administration is usually custom automation. There are a lot of tools for this, and they all have good and bad, so you should just go with what is most accessible to you.
Nagios is pretty standard for monitoring. Administration is usually custom automation. There are a lot of tools for this, and they all have good and bad, so you should just go with what is most accessible to you.
Maybe, it is good way to use one of them, but it so hard to find day for configuration of all of this =)
Dead simple to install and use. Fancy graphs, lots of useful plugins for monitoring processes.
Using it for more than a year, no problems, responsive support. $15/server/month.
What would your ideal monitoring system have? Would it be web based? terminal based? Zero install effort or full customizability? What would you like to monitor? Just monitoring? Alerting too? Just servers or also containers?
I just use terminator terminal, multi-terminal grid. One terminal per server showing htop via ssh. http://gnometerminator.blogspot.com.au/p/introduction.html http://hisham.hm/htop/
Currently I just use pingdom to check availability, but I'm really interested on other people needs, so I'm more interested on a related set of questions: What would your ideal monitoring system have? Would it be web based? terminal based? Zero install effort or full customizability? What would you like to monitor? Just monitoring? Alerting too? Just servers or also containers?
Monitoring:
- resource usage (hdd, cpu, ram, network, LA)
- server status (online/offline, uptime, response time?)
- package manager status (new packages)
- services status (running/not running, etc)
Notifications: - allow to add triggers (with some default triggers: high cpu/ram/network/LA usage (90-100% 5 minutes), high hdd usage, etc.) with notifications through email/hipchat/slack
Server control: - restart server?
- package manager: update packages
- services: start, stop, restart
It must be web based with zero install effort. I'm doesn't use containers enough, but maybe it will be useful feature.exec('uptime',$response); echo $response;
In around 15 minutes I now have a siri like bot to take with me that will alert me to anything funky which is necessary after a week of some rogue processes.