Zabbix Reviews

Our primary use for the solution was to monitor the network and servers.

We used this solution for monitoring our applications and our internal web applications, which we couldn't do with Icinga (the previous software we used). That product was very good but the application monitoring of it wasn't good at all. Now I hear that application monitoring is very good in Icinga EN, so we might try it again.

The most valuable thing about the Zabbix product is that it was easy to install and manage.

There are a lot of things that can use improvement which is why we are seeking a new solution. Network monitoring is a problem. It gives too many false positives. For example, it notifies us that a server is down while I'm using that server — the server it claims is down — to do the search. A moment after the search is complete, everything is OK again. It's called flapping. It has some flapping control, but it's not as good as other products. I used to use Icinga and it is a better product in that respect.

I know it doesn't just go dead on me, so the stability is okay I guess. 

I don't really know how the product scales as I haven't tried to scale it up or I haven't had the need. Considering that we will be moving away from the product, I don't need to bother with that right now.

Their online help is okay, but not as amazingly good as Icinga, for example. Icinga has the largest user base as far as I can tell and I use IRC for help a lot and there's a lot of people in it. There are few helping with Zabbix. The forums are pretty up-to-date.

As far as tech support itself, I have emailed them about the flapping issue, but the main issue that bothers me is the flapping and infrastructure monitoring which is not very good. The support team suggested a few tricks which would help but not as much as I want. The support team is responsive, but nothing was resolved.

We are actually looking for another solution that meets our needs better. That is not because Zabbix is necessarily a bad solution. Our needs changed and there are better solutions available.

I previously used ManageEngine OpManager in another organization, so I guess the reason as to why I switched was that I changed jobs. That product was excellent, but it is also out of the reach of my current budget.

Installation was not hard and it was very straightforward. The initial deployment without any complex setup took a few hours. Then the setup took an additional three days to a week. In total about a week to be completely deployed with all the servers monitored and everything working.

I did the deployment alone. I set it up and everything, and left it to other people to monitor as per their responsibility. I have 10 admins monitoring it. I've stopped monitoring it at this point, or in the half past year or so, as I am looking for a better solution.

The admins use it daily. Even now, I'm getting all the emails and I'm a little bit bothered from the continued flapping. Every admin is responsible for a different aspect of the monitoring so they get their dedicated reports. For example, one admin is responsible for the ELP servers, so he's getting only the email for the ELP related stuff.

We did not implement through a vendor. I did the implementation myself. It's very easy, you don't need anyone just to install it. For more complicated stuff that I was not sure of, I asked around on forums. I did the entire implementation myself and it's very easy.

Any product that is saving you from a network meltdown is really worth more than you pay for it. This product did its job and some are still using it in the organization while we search for a better solution.

I would rate this product a 7 out of 10. This is because it needs better flapping control and better infrastructure monitoring. Other products provide this already. I don't think I have much to say that isn't answered elsewhere. The product's benefit is that it is easy to get up and running. 

To monitoring our prod, pre-prod, and test environments.

Simple, we know everything about our infrastructure, problems, etc.

• DBforBIX
• Auto-discovery.

It's OK for me as is, but some frontend improvements would be nice.

Infrastructure monitoring.

Excellent monitoring tool.

Auto-config.

Multitenancy.

• OS monitoring with SNMP or Zabbix agent (Windows(server and client), Linux and mac)
• Database monitoring with Zabbix agent (mariadb-oracle)
• Device monitoring whit SNMP (Cisco devices, Mikrotik and firewalls like sophos nad juniper)

Creating a trigger to get alarmed on it and take action to solve them (automatically), and get management info to improve performance.

Zabbix scripts is the most valuable feature because you can execute a custom script on devices to solve problems in seconds.

It is a little complex to config and implement so I'd like for them to make it easier to config, for example, a configuration for SNMPv3 or trap listener on it.

We still do not have this software completely under the stress, but it has worked well so far.

Like other software, its efficiency and scalability depend on a variety of circumstances, one of the most important is to allocate enough resources to it and its database.

There are good resources to help with fixing your needs.

And while this is an open source software but has a good support team, however, we have not had the support needed before.

Because zabbix is a open source NMS however it is very powerful and highly scalable.

Its launch is more complicated than other software and requires more steps for settings. But when it comes to how it works and how to categorize the information in the database, you'll have a better idea of what you can say.

We did this ourselves.

Of course, as with other network management software, the return on investment depends entirely on management responses to the information that is available from these systems.

This is definitely a free software (it's open source), and You just need to allocate some resources to launch it

Of course, we compared it with similar tools like Nagios, Zenoss, PRTG and OP Manager , and we chose it based on the benefits

When you learn how to work with it, you will love it.

It is a complete network management system that will meet all your needs.

We have a lot of servers (about 10,000). We monitor and manage them using Zabbix.

It has rich functions.

The financial setting is the most valuable feature, since Zabbix can use old data to current data to set the threshold. We can use previous data to set the threshold.

I want Zabbix to improve the UX/UI. Zabbix doesn't use a JavaScript chart for images, and I want them to improve this.

Performance is really stable.

It is scalable.

We don't use technical support. We have a contract, but we don't use it because there are not many problems.

We switched from our previous solution because of cost.

I installed Zabbix, and it was easy.

It is free, which allows us to reduce costs.

Our choices were Geneos, Nagios, Zabbix, Centreon, and Cacti. We chose Zabbix because we did a proof of concept, and Zabbix was the best. It had the richest functions, and it was free.

I would rate this solution as a 10 out of 10. It is the best product. I really love Zabbix because it has a lot of functions and works well. My advice is to use Zabbix.

When selecting a vendor, the number of customers is very important along with the price.

We use it to monitor Linux systems. It has performed well.

We are able to do problem determination on runaway processes. 

Graphing processes. It can send messages to our ticketing system. It has good graphs of what is going on within the operating system.

I would like to better be able to monitor Oracle processes.

The stability is good.

The scalability is good.

I have not used technical support.

We did not previously use a different solution, so I asked my manager to look into it.

I was involved in the initial setup. The initial setup was straightforward.

We evaluated SCOM.

Most important criteria when selecting a vendor: 

1. Features
2. Price.

Monitor systems and networks devices and web applications. Increase monitoring by including powershell script and automation on incidence responses.

We are now more pro-active before an issue appears to our customer because all the layers are now converged by Zabbix monitoring.

In addition, this monitoring product is easier to maintain, configure and less expensive in the total cost of ownership than the others.

The most valuable features are its performance (scalability) in monitoring, the monitoring centric (agent compatibility with the large vendors OS, SNMP, IPMI, JMX), VMware monitoring, web monitoring, capacity planning and the proxifying monitoring.

The capacity planning feature and SLA monitoring need to be improved.

The capacity planning feature should give to administrator recommendations regarding the actions to be done on systems to ensure scalability and stability. In addition, currently this feature only provides basic information (disk usage time left, cpu consumption forecast, etc.). You cannot predict easly the capacity planning of virtual infrastructure or scale-out network storage.

There were no stability issues experienced because the server component is compiled in C and is separated from the web dashboard (PHP).

There were no scalability issues experienced because Zabbix is optimized for a high performance. The Zabbix server and the Zabbix proxy use various data caching solutions, giving them great performance and reducing the load on the back-end database.

We have a partnership with a solution integrator, so we don't open a case directly with Zabbix LLC.

Previously, we were using Nagios coupled with Centreon. We switched because Centreon has some paid features and so, there are some hidden costs. In addition, we needed to use an agent in our client OS because some metrics are deprecated by SNMP and are only available via WMI; WMI is known for its performance problem in monitoring.

The setup was very simple, it is very well-documented and packaged for a lot of Linux distribution.

This product is free, i.e., no vendor lock and all the features are included without the Enterprise Edition. However, just like the other products used in production, it's better to subscribe to a support contract.

We looked at other solutions; stay with Centreon's newer version.

The only advice is:

• To read the documentation before implementing.

• Test the software with the appliance (i.e., only for testing and not for the production environment).

• Participate with the community on the forum.

• Monitoring servers
• Health and communication links availability

By using the solution, we moved from a reactionary approach to a proactive evaluation of our equipment/systems.

Look and feel.

Six years.

Not in the version we’re currently using.

No.

We only use the free version without support.

Yes, we used to use another solution. We migrate to Zabbix after evaluating when it was implemented as a part of a web-based software solution that was acquired by the company in which I was working at that time.

The installation process was simple.

Nothing, because we’re using the free version, which covers all our current needs.

No.

You’ll be pleasantly surprised if you give the product a chance.