commentBlock = $("#comment_post_29488").find('.comment-blocks'); commentBlock.find('.loading').hide(); commentBlock.find('.see-all-comments').hide(); commentBlock.html("
<\/a>
\"it_user216399<\/a>
it_user216399<\/a>Senior Network Engineer with 1,001-5,000 employees<\/span><\/div>
<\/span>Real User<\/span><\/div>
<\/i><\/div>
<\/i>Report as inappropriate<\/a><\/div><\/div><\/div>

So what you guys suggest if a company have 25000+ employees and thousands of network devices to monitor worldwide ? Currently we are using Solarwinds and we need to follow a distributed environment . We are looking for a centralized setup where are nodes can be managed and monitored from one location including the configuration backup and reporting. Any suggestions ?<\/p><\/div>

<\/i>Like<\/span>(0<\/span>)<\/a><\/i>Reply<\/span><\/a><\/div>
<\/div><\/div>
<\/a>
\"it_user76665<\/a>
it_user76665<\/a>Engineer at a tech vendor with 51-200 employees<\/span><\/div>
<\/span>Real User<\/span><\/div>
<\/i><\/div>
<\/i>Report as inappropriate<\/a><\/div><\/div><\/div>

Thank you Patrick<\/p>\n\n

You are right it is not a fair comparison for Zabbix. But I just wanted to add that I never like Nagios in the first place and was never an expert of it because of the complex configurations and all the different file relationship you have to manage. So what OMD stands out from Nagios is that it abstracted away all that complexity for you so you don\'t even need to know what\'s running in the backend, everything is nicely integrated and presented with one UI just like Zabbix. No effort required for integration, no need to understand how Nagios works, you just need to learn how OMD works. <\/p><\/div>

<\/i>Like<\/span>(0<\/span>)<\/a><\/i>Reply<\/span><\/a><\/div>
<\/div><\/div>
<\/a>
\"it_user8784<\/a>
it_user8784<\/a>Consultant at a tech consulting company with 1,001-5,000 employees<\/span><\/div>
<\/span>Consultant<\/span><\/div>
<\/i><\/div>
<\/i>Report as inappropriate<\/a><\/div><\/div><\/div>

Off course I read it 3M values per minute that\'s less then 900 vps still far below what zabbix is capable of. \n
But I was with slow pointing out to the graphs part. \n
People just fail in zabbix on the DB part you need descent hardware and good database tweaking.\n
To many people want to visualise these days and zabbix should not be virtualised it needs descent hardware.\n
Like I wrote before api makes it more complicated but should not be the reason for not choosing it. \n
I do agree it would make life more easy with files. I just dont agree with the arguments in the article like that more contributors would make it a better alternative as zabbix keeps development more in house each contribution needs to follow strict coding rules and its written in C making it less easy to contribute. \n
What people not know is that many new features in zabbix like VMware monitoring are complete sponsored implementations by companies. Don\'t get me wrong I not say that omd is bad it\'s probably the best solution if you already have a monitoring solution based on nagios or if you have nagios knowledge in house. But for a new setup i would really compare them both more in depth then what the article did as the reasons they showed to not chose zabbix are not really valid.\n
ATM i use glpi + ocs<\/p><\/div>

<\/i>Like<\/span>(0<\/span>)<\/a><\/i>Reply<\/span><\/a><\/div>
<\/div><\/div>
<\/a>
\"it_user76665<\/a>
it_user76665<\/a>Engineer at a tech vendor with 51-200 employees<\/span><\/div>
<\/span>Real User<\/span><\/div>
<\/i><\/div>
<\/i>Report as inappropriate<\/a><\/div><\/div><\/div>

Did you even read the performance part of the article? What\'s the performance of Zabbix? https://mathias-kettner.de/checkmk_checkmk_benchmarks.html\n
And OMD is not just about files, it has API too, and I am using it\'s API to do automation. CMDB is a good idea, which one do you use?<\/p><\/div>

<\/i>Like<\/span>(0<\/span>)<\/a><\/i>Reply<\/span><\/a><\/div>
<\/div><\/div>
<\/a>
\"it_user8784<\/a>
it_user8784<\/a>Consultant at a tech consulting company with 1,001-5,000 employees<\/span><\/div>
<\/span>Consultant<\/span><\/div>
<\/i><\/div>
<\/i>Report as inappropriate<\/a><\/div><\/div><\/div>

It\'s a package but you still rely on 3rd parties.\n
The link you point at talks about failing clients in zabbix 1.8\n
zabbix is now in 2.2 and almost 2.4 even in 2.0 i never had a client crashing.\n
and Slow graphs in zabbix ?? My experience is just the other way around, I come from nagios forks and they where painfully slow compared to zabbix. Also the number of values per second that you can monitor with zabbix is much much higher then with nagios.\n
Yes files are more easy to manage with puppet ansible chef .... Puppet has modules for it i think but yes it makes it more complicated but on the other hand the api makes it easy to communicate with other software. \n
The cmdb is limited but who cares for that i use a real cmdb program and let zabbix just feed it with the api.<\/p><\/div>

<\/i>Like<\/span>(0<\/span>)<\/a><\/i>Reply<\/span><\/a><\/div>
<\/div><\/div>
<\/a>
\"it_user76665<\/a>
it_user76665<\/a>Engineer at a tech vendor with 51-200 employees<\/span><\/div>
<\/span>Real User<\/span><\/div>
<\/i><\/div>
<\/i>Report as inappropriate<\/a><\/div><\/div><\/div>

That\'s why you need to look into OMD (Open Monitoring Distribution), it aggregate the most powerful 3rd party plug-ins for Nagios into one easy to install package. No individual installation required and historical data are kept for reporting. Please check out the blog post I made for more detail on why OMD is a better choice. http://blog.unicsolution.com/2013/11/best-monitoring-solution-omd-nagios.html<\/p><\/div>

<\/i>Like<\/span>(0<\/span>)<\/a><\/i>Reply<\/span><\/a><\/div>
<\/div><\/div>
<\/a>
\"it_user8784<\/a>
it_user8784<\/a>Consultant at a tech consulting company with 1,001-5,000 employees<\/span><\/div>