Zabbix Reviews

The solution is primarily used for monitoring servers, printers, and network switches.

It's very easy to use and manage.

The solution is stable.

You can scale the product well.

There is a free open-source version of the solution.

I don't like to use the solution for the most part.

I get too many false positives. I get a problem one minute and then it's okay the next. That happens a lot. I hate that.

The user interface could be better.

The performance needs improvement.

I've been using the solution for six years or so. I've used the solution for a while at this point.

I don't have any issues with the stability. The performance isn't great, however. That said, it doesn't crash or freeze. There aren't really any bugs. 

The scalability is good. A company can easily expand it.

We have about five users who monitor it constantly. I no longer manage it myself. 

I've never contacted technical support. I can't speak to how helpful or responsive they are. 

I need to be able to monitor stuff and I can't monitor these things now, so I am using other products for it.

The installation happened a long time ago. I can't recall what the implementation was like in terms of if it was complete or straightforward. 

You only need one person to handle the maintenance. 

I'm using a free version. I do not pay any licensing fees.

I'm a customer and an end-user.

I'd rate the solution at a seven out of ten.

I'm not sure if I would recommend the solution. I really don't like it as it generates a lot of false information. That said, it is a good monitoring solution, for what it's worth.

The solution is open-source. 

The infrastructure monitoring is great. Then, Zabbix being open-source, and with the whole platform, we have good network monitoring there. You have these ping monitors, synthetic monitors, that are really helpful.

The solution can scale well.

Technical support is great.

The pricing of the product is reasonable.

For internal monitoring and network monitoring the solution is really good.

It's open-source software, and due to that, they really don't have legacy service monitorings like APM, or build-on capabilities, and the pure part of the transaction-related data. It is good for internal network monitoring, however, it's not for the service we are monitoring, microservices.

The stability could be better.

Basically, they need to provide automated monitoring, synthetic monitoring, and then APM monitoring as well as more on microservices or technology space, maybe like Java, .NET, Datadog, et cetera - these kinds of add-on instrumentations. They need to work somewhat on the dashboard and alerting side. Dashboards are not that good. They can improve on them.

With Zabbix, I just started as an open-source strategy moving from the enterprise version. It has been six months.

It's not extremely stable. 

n terms of infrastructure, you have to tune based on your requirements. You're monitoring 1,000 or 10,000 systems, so it depends on what you're monitoring, and you have to tune it. They don't have a tuning table or sizing recommendations. However, they have the beta version of it. Certainly, on the console side, they need to improve a lot in terms of stability and performance, and bottlenecks of the product. Whatever data we process with Zabbix goes to Postgre or MySQL. Right now, we are trying to use Postgre. They are using it to do a lot of time scaling stuff so that we can support SQL data. However, it seems like they have limitations with the Postgre database.

The solution is scalable. We have admins and users and 50 IT people on it. However, the systems we are monitoring are more than 10,000. You can monitor more than 10,000 UIs. That's our target.

We are using the open-source version and therefore we don't get technical support. However, if someone wants to opt for it, they can get it and technical support is great, even though we haven't used it yet.

The pricing is very reasonable. Zabbix is very cheap. Compared to other tools like Nagios and others, Zabbix is very cheap.

If a company wants to implement the solution, I suggest they go with the latest version. It is a stable version. Preferably they should use it with the database, and not the AWS database, as it doesn't give you time scaling. You have to install your own Postgre and you can apply the time scaling feature in that. That way, you can add your data competition to Zabbix. 

You have to do a lot of tuning on cache and view sizing. If your clients are on a remote site, you usually use proxies. Therefore, data will be sent to proxies, and then from proxies, it will be sent to the server. 

I'd rate the solution at a seven out of ten.

We are currently doing a POC. For now, it is our testing tool.

We use it mostly as a monitoring infrastructure for services and applications, and it also monitors the capacity.

As we are still in the test phase, we have not yet explored all of the features offered in this product.

It's a flexible solution.

My main intention is to support or use Zabbix to report patching for servers, or to somehow maintain the patching from Zabbix.

Outside of the normal standard monitoring, I would like to extend patching, importing patching, and supporting patching for Windows Servers.

I have been using Zabbix for one year.

We are using the newest version.

Zabbix is a stable solution.

We have not yet tested the scalability of this solution. We tested it on a small group of devices, so it is difficult to say at this time.

We intentions to install more features on the device. During the testing, we don't have all of the resources to manage all installations.

We have approximately 40 users in our organization who are using Zabbix.

We have contacted technical support from Zabbix, and have spoken with partners from Poland. 

I have more experience with the WhatsUp Gold Monitoring tool. I still have WhatsUp Gold but we are going to replace it.

We are testing other tools that are free.

The initial setup was straightforward. It was easy.

With the help of suppliers, it did not take much time to deploy. It was not complex.

As we were using it for testing, we were using suppliers.

We will need a team of experts for this solution as well as some external support.

There is no license but we need to pay for support.

Zabbix is an open-source solution.

I would recommend this solution to others who are interested in using it.

With my current experience, I would rate Zabbix an eight 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.

We use this solution for network and application monitoring.

The solution is open-source, easy to manage, and user-friendly making it easy for anyone to use.

Zabbix is always improving by adding more features and they have monthly announcements explaining the upcoming new features and functionality.

The automation could be improved.

In an upcoming release, there should be automated reports which we are currently doing manually. For example, if we collect a report file every day and want to send it to a moderator for review. We are expecting this feature to come out soon but it would be valuable to have now.

I have been using this solution for approximately four years.

The solution is stable. They release major updates every two or three years with the minor changes being released every six months.

The solution is scalable.

The initial setup is straightforward.

We have evaluated other solutions. 

I rate Zabbix an eight out of ten.

We use this solution to monitor our network devices.

The performance and bandwidth are valuable features.

The performance reporting could be improved.

I have been using this solution for approximately two years.

The stability could be improved, there are some limitations.

We have 11 people using this solution in my organization. We have four engineers and six technicians that do the implementation and maintenance of the solution.

The technical support is good. However, the support could be more knowledgeable.

The installation is straightforward and it took approximately one hour.

We did the installation ourselves. However, I had to watch some video tutorials and view some PDF help files online to complete the installation.

There is a license required for this solution and we pay annually for our license.

I would recommend this solution to others.

I rate Zabbix a seven out of ten.

We are using Zabbix in our project for demo purposes. One of our clients is also using Zabbix. They have a data center, and they use it for internal monitoring. They are on a cloud system.

It is a great product. The SNMP protocol tracking feature is good. I really like how it tracks SNMP. The alerts are also great. 

Its UI needs to be improved a little bit more so that an end-user is also able to handle it. I can handle it, but others should also be able to handle it in a better way.

It becomes complex when we are growing and need to add proxies. We need more scalability features and documentation for different use cases. A lot of articles are available, but they need to be in proper documentation. For example, when you have thousands of servers that have to be monitored in different regions of the world, there should be some kind of documentation to describe how you can create proxies and add them. Sometimes, when you are using the database, it can get overloaded. When the network is growing, the number of transactions becomes very high, and the database gets overloaded. There should be information about how to reduce the load on the MySQL database, which is what Zabbix is using. 

The market is growing a lot, and it should be enhanced for a lot more things. We are currently bringing enhancements at our end for different use cases. For example, when dockerization is going on, how can we check the logs inside the Dockers. We should also be able to monitor and check the number of logins and add features such as SSO login and two-factor authentication as a protocol. These are the security features and concerns that we have to deal with. Currently, we are developing modules to add features to Zabbix, but they should also work on these features.

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

It is stable up to a level. 

When you are growing and need to add proxies and other things, it becomes complex. To deal with this kind of complexity, more scalability features and documentation for different use cases are required.

I did not connect with Zabbix support, but the client's team connected with them. I worked with the client initially, and after that, I gave them access and everything else. They directly sync up with Zabbix's support team.

The initial setup is great. However, later on, when you are scaling it, it becomes complex.

Its licensing is fair. It seems to be much cheaper than others.

Zabbix is a good product. It just requires a better development model, better UI, and better scalability. It also needs more features.

I would rate Zabbix a seven out of ten.

I use the solution for network monitoring. When I was in engineering school I used this solution and I found it really good. I wanted to bring the functionality of this solution to my community to show the engineers in my enterprise. There is not a lot of understanding of network monitoring and I am hoping to bring to them my knowledge. 

The solution's design has recently changed and it is visually pleasing with more color, for example, there is blue, black, and white. If you are a new user it is very simple, you do not need to be highly technical to use it. You can rapidly learn how to use this solution.

When using this solution in enterprise monitoring, you are able to see that there are some issues with equipment that could be causing a problem. Sometimes you want to make a root command that you do not want to be executed automatically. What we have tried to do is open an SSH session directly from the solution's interface but it is not possible. I have heard from others that there are scripts that can manage this task easily but I have not figured it out. In the area of the solution where you write the command, it is not very user-friendly and could be improved. We want the ability to write commands and execute them manually.

Additionally, I would like the ability to be able to have network mapping for this solution. I use network mapping to monitor networks and there are not very many tools that are able to do it or if there is a tool, it is not easy.

The color scheme of the interface could improve by allowing more variations or user customization.

I have been using the solution for four years.

The solution is stable. 

We have approximately 10 people using the solution in my company.

In my community, we were previously using Nagios and Cacti.

The solution is free. However, many open-sourced tools start out free but eventually start charging, I hope this solution stays free. 

I rate Zabbix an eight out of ten.

We use Zabbix on-premises for monitoring our servers and calculating consumption of CPU, memory, and storage space. It's an important part of monitoring our environments and it shows us a lot of information about the health of our systems. And, in terms of performance, we also use it for actively getting rid of bottlenecks.

There are four IT staff members who use Zabbix regularly, including system administrators and the director of IT.

With Zabbix, we can be proactive in eliminating problems with over-consumption of resources, such as with memory, for example.

The most valuable features in Zabbix are those that help us overcome bottlenecks in CPU usage, as well as reduce memory delay. I know that we have only reached the tip of the iceberg of what Zabbix's features can do for us, and we have not used all of them yet.

I think the reporting part of Zabbix can be improved in terms of more user-friendly graphics to display the collected data. Many simple users who don't know how to use Zabbix properly might get confused by the reporting, although at the same time it is very versatile for my company.

I've been using Zabbix for three years.

There have been no issues with stability.

We don't have much need to scale Zabbix, virtually or otherwise, or increase its usage beyond current levels, but I think it is simple to do.

We were previously using Nagios, but with Nagios the reporting features are very poor. If you want to improve on the reporting with Nagios, you have to construct other features and software on top of it, whereas Zabbix is more to the point and straightforward.

Zabbix's reporting isn't very good, either, in my opinion, but it's better compared to Nagios.

The setup was easy.

Regarding the installation of Zabbix, we did it by ourselves and it was easy enough. Our branch's environment is pretty simple and we don't have many complex requirements.

We were searching for an open source solution and Zabbix fit the bill because it is free and open source under the GPL license. 

My advice is that the person who is responsible for implementing Zabbix in their environment should be familiar with Linux because then the process is more simple, efficient, and takes less time.

I would rate Zabbix an eight out of ten. 

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.