I vote for Zenoss Core (http://www.zenoss.org/) - takes care of both
performance monitoring & events/alerts, with very flexible events
processing.
For some reason less popular in Israel when Zabbix, but has very impressive
list of US customers.
regards,
Vitaly
PS: presented Zenoss for ILTechTalk
On 16 June 2014 19:11, E.S. Rosenberg wrote:
> Amos - can you add a TL;DR about your mail?
>
Nagios and its ilk are not scalable or efficient, resulting in very complex
setup and too slow event discovery.
Zabbix is not a good fit if you want to have an automatic setup using
things like Puppet.
_
Zabbix, nagios (which focuses more on alerts/checks but can be extended to
graph) or cacti (which focuses more on graphing but can be extended to do
alerts) are all excellent solutions.
Amos - can you add a TL;DR about your mail?
Regards,
Eliyahu - אליהו
2014-06-16 11:44 GMT+03:00 Rabin Yasharz
On Mon, Jun 16, 2014 at 11:25 AM, Amos Shapira
wrote:
> How do you configure zabbix outside its GUI? As far as I saw so far it's
> not possible so you have to point and click your way through its gui.
>
Yes, can be a lot of work at first, and the lack of proper
"auto-discovery" & device detecti
How do you configure zabbix outside its GUI? As far as I saw so far it's
not possible so you have to point and click your way through its gui.
Most of what I wrote against nagios is relevant to Zabbix as well - central
server etc.
On 16 Jun 2014 17:49, "Rabin Yasharzadehe" wrote:
> I can recommen
I can second Zabbix.
We use it in our current setup 100+ servers, works OK.
Also you can take Nagios. or one of the clones
One of previous my previous monitoring solutions had 1+ specialized
requests/hour with help of custom scripts in perl & C.
One thing to consider.
Most of monitoring soluti
I can recommend Zabbix, I was never used it on a large network (~30 server
most), but i was happy with it.
- you can set the monitoring interval for each item (from 1s -> days)
- samples are stored in the DB, and graphs are plotted only when you need
them
- have a build in support for SMS and Jabb
Another thing - while I was digging the Sydney DevOps meetups for a talk
about monitoring by a dude from Google, I stumbled across a reference to
InfluxDB: http://influxdb.com/.
On 16 June 2014 10:49, Amos Shapira wrote:
> For a start, it looks like you put both trending and alerting in one
>
For a start, it looks like you put both trending and alerting in one
basket. I'd keep them separate though alerting based on collected trending
data is useful (e.g. don't alert just when a load threshold is crossed but
only if the trending average for the part X minutes is above the threshold,
or e