Zabbix Reviews

It monitors almost everything.

It provides high scalability, alerting, notification, templating, and end-to-end security.

By proactively monitoring, it helped us to fix problems before any major disaster.

There are a lot of areas for improvement, specifically in the dashboards and reports functionalities.

I have used this solution for four years.

There were no stability issues.

There were no scalability issues.

I haven’t used technical support yet.

The initial setup is a bit complex, as lots of things need to be planned carefully during the implementation of the solution, such as the hardware sizing, customizing templates for monitoring the customer's environment, and much more.

It is a true open-source solution, so there are no licensing costs.

We evaluated many products such as HPE SiteScope, Nagios etc.

An in-depth knowledge of the product is needed to customize it, according to your customer's needs.

It is advisable to hire a consultant and do a PoC (proof of concept) before arriving at conclusion.

We use this solution to monitor, install and configure our networks, servers, virtual machines, and cloud services.

We like the user-interface for this solution, which makes it an easy to use tool.

This product is also easy to configure to our exact requirements.

We would like to see the addition of automatic push functionality to this product. This would save time when monitoring our servers and networks as, at present, we have to manually install the Zabbix agent on any hardware to be monitored.

We would also like inventory management functionality to be added to this solution.

We have been using this solution for three months.

We have occasionally experienced issues with the stability of this solution.

This is a scalable solution, but requires a lot of resources to be engaged in order for it to be scaled.

The setup process for this solution could be easier, as it requires a lot of configuration prior to deployment.

We implemented this solution in-house.

We would rate this solution a seven out of ten.

My primary use case is switch and database monitoring.

The most valuable feature is the protocol to manage anything.

An area for improvement would be the ease of doing aggregation from the value or different devices.

I have been using this solution for three to four years.

Zabbix is stable.

This product is scalable.

The initial setup was easy, and deployment took two to three months.

This solution is very good for data reporting. I would rate this solution as ten out of ten.

We are using Zabbix just to monitor our small network out here.

The integration with third-party tools and the alerts are most valuable.

We would like to monitor other touchpoints such as ATM machines. It would be great if it can provide monitoring of ATM machines. Compatibility with other products would also be great.

We have been using this solution for two or three years.

It is very stable.

It is scalable. We have two people who are using this solution.

There are a lot of professionals and sites available, so we just get help from them.

We were not using any other solution.

It is reasonable.

Our requirements are basic, and it is fulfilling them. I would rate Zabbix a seven out of 10.

Infrastructure monitoring.

Excellent monitoring tool.

Auto-config.

Multitenancy.

We are using Zabbix as our network monitoring solution. We are now trying to understand how to use the service assurance functionality, as we would like to leverage Zabbix for this task.

The most valuable feature is service assurance.

The interface is pretty straightforward. As long as the agent is running on another instance and Zabbix is able to connect to the agent, we haven't seen any issues.

Zabbix claims that there is an auto-discovery process but my team member was facing difficulty and was told that it's not really automatic, and there are some manual steps. 

We have been working with Zabbix for the past month. We are conducting a proof of concept with it.

We are not yet using Zabbix very much. We have spawned the Zabbix server and only a couple of AWS instances are running, which it is monitoring. This is to make sure there are no billing problems in AWS. At the end of the day, we stop the Zabbix monitoring. The next day when we come in, we start it again.

At this point, with our limited usage, we have not seen any issues with stability. Perhaps, once it has been running full-time for a week or longer, we may hit those types of issues.

During our PoC, we only have two technical people working with it.

This is the first monitoring product that we have worked with. Prior to this, we were dealing with NMS and CMS products.

The initial setup was pretty straightforward. We did not face any issues and it was up and running within a day.

Our in-house technician completed the deployment.

This is an open-source solution that can be used free of charge.

At this point, it is too early for me to recommend Zabbix one way or the other, as we have just scratched the surface of its capabilities.

I would rate this solution a seven out of ten.

We are implementing this solution for our clients. 

What we find the most valuable about Zabbix is that it is open source and there are no licensing costs.

While there are a number of benefits to Zabbix being open source, getting that trust from the customer is a little bit on the challenging side. Implementation is always tailored to the customer and the kind of information we need from the client to carry it out can make them very uncomfortable. Sometimes the clients are not ready to share it.

It can also be difficult for us to formulate a price for clients that need a solution for which there is no template. If we can implement a solution with the help of a template, we know how much time and effort it will take so it is easy to estimate a price for the customer. Without templates, estimation is a little bit challenging. 

In addition to the above, although there are templates available for Cisco switches, they do not work for all families of Cisco switches.

These are the challenges we are facing at our company. Overall, setting up Zabbix is a challenge. However once it is setup, managing it is comparatively easy.

We have been using Zabbix for a year, I suppose. 

Zabbix is quite stable once it is set up. We haven't had any post-setup issues. 

We are regularly in touch with Zabbix's technical support. Generally, there is little bit of challenge because of the time zones. Nonetheless, their tech support is not bad. It's good.

We did not previously use a different solution. Zabbix was the first solution we worked on. However, right now we are in the process of exploring other solutions.

We are evaluating Motadata. This is a solution based out of India. We are in touch with them, but we are in the very initial stages. We also don't know how it will work out.

Whether or not setup is straightforward or not will depend on the client's use case. From our end, the issue is estimating the effort it will take for us to implement the solution for our clients. We run into issues when it comes to giving the clients a quote for our work ahead of time. 

Because Zabbix is an open source solution, a lot of customization is required. In turn, a lot of information has to be provided by the client about exactly what they want, which parameters they want to monitor, and what the thresholds are. Proprietary solutions would already have those thresholds in place. Once this process is done, it's really very good for your organization. But it does take a lot of work.