Zabbix Reviews

We use it to collaborate with each other internally as a company for video conferencing, meetings, teams, and those kinds of things. We implement it in customer environments as well for the same reasons, and also for eHealth solutions, for instance, in hospitals.

It improves the way we work, the way our customers work. With eHealth, for instance, surgeons can make appointments with patients at a distance and they can still see each other. That's very, very good.

The most valuable aspect is it's very robust. It has a lot of features and it also integrates with a lot of the Cisco hardware around it, such as Smartboards, video conferencing units, et cetera, et cetera, et cetera. It's a really robust and complete solution.

The initial setup is easy.

It's a stable solution.

We find the product scalable. 

The use is very straightforward. It's actually pretty much ready to go out of the box. It's very easy to start using it, to be honest.

You can also integrate it without Microsoft Office 365 and put it in the agenda of Outlook for instance, for meetings.

They've already added extra features, such as noise-canceling and facial recognition, which is great.

One of the things we don't like is that Zabbix has a license structure with a price that is high compared to the competition. It's very high, for example, compared to something like Microsoft Teams.

We have used the product since Cisco acquired it. It's been maybe ten years or so at this point.

The stability is great. There aren't bugs. It's not glitchy and it doesn't freeze. it's reliable.

The scalability on offer is good. If a company needs to expand it, it can do so. 

All of our people in the company in Europe use Zabbix for sure. That's at least 1,000. We also use it for events to stream video content, to customers, for instance, on a fairly large scale.

Technical support is very good. We have straight contact with the Cisco technical assistance center. If there is anything that has to be changed or improved, then we can directly call them.

We previously used Microsoft Teams. The number of possibilities in Zabbix was better than in Teams, and it also integrates very well with the hardware solutions from Cisco which was why we switched.

In general, the initial setup is very straightforward. It's not a difficult implementation process.

There isn't much staff needed for deployment or maintenance tasks. 

If more functionality is added to it, that might be a reason to use it more and more. However, as it is, at this point, we are already intensive users.

We buy the solution yearly. I'm not very aware of what the actual pricing and the licensing are, however, I know that for extra features, there is a possibility to buy a little bit more.

We looked at Zoom, however, we never ended up using it. 

Currently, we use it and we implement it as a partner.

We're always on the latest version. It's automatically updated via the cloud.

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

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.

Generally, it is used for infrastructure and network monitoring. We've been using it for monitoring systems and application infrastructure. It goes through the whole stack, and that's what we like about it. It can also be extended, but I wouldn't consider that as the primary use case. 

It can be deployed on-premise as well as on the cloud. It is meant to be on-premise, but some providers like us can use Zabbix on the cloud and provide it as a SaaS model. It is predominantly deployed on-premise. We mainly use versions 4.x and 5.x.

Just like any monitoring tool, the major benefits would be being proactive about and avoiding downtime and being able to do capacity planning of the infrastructure. It is about having more knowledge about what you own in terms of infrastructure. Once you do that, you're able to make educated decisions. They are not guesswork.

Its overall flexibility is most valuable. When our customers have some custom applications that are not necessarily covered by the community or a standard monitoring tool, we use Zabbix to build our own modules with our own templates. This feature has been useful in using Zabbix for infrastructure and IT monitoring. It has also been useful for industrial equipment monitoring.

Zabbix is very lightweight. It is efficient in terms of performance because it doesn't use a lot of resources. 

Its UI should be improved. They did some improvements in version 5, but it could benefit from some more work. 

Its integrations should also be improved. They've been active for one year, and they seem to have noticed that. It has new integrations, but it could benefit from more integrations. 

As far as I know, there is no model to push statistics, metrics, or events towards Zabbix. This type of API isn't yet there, whereas some other tools provide an API for this.

We have been using this solution for around five years.

It is very stable. We've had it in our customer environments for four years, and the only thing we had to do was to tune the database because we have more metrics. It never went down. 

One of our customers is monitoring a few hundred devices. It can be used for a few thousand devices without much complexity, but beyond that, it is difficult to scale. We don't use Zabbix beyond that, and we try to avoid it for larger deployments. You can create a distributed setup that helps with scalability. They have a distributed collector and a proxy that can be used for that.

It doesn't consume a lot of resources and is efficient in terms of performance. You can put it on a Raspberry Pi and monitor a few devices. If you push performance to the limit and have too many devices, I'm not sure how good it is then.

Our customers have subscribed to technical support, but they never really used their technical support. Zabbix has never failed. Our guarantee had expired, and we started our own maintenance on top of Zabbix with some government clients, but we never had to use Zabbix support.

Its initial setup is very straightforward. You need prior knowledge of Linux, but you don't need specific knowledge of Zabbix to deploy it. It is really straightforward and lightweight. Its deployment could take as little as one hour per person.

You simply download the packages. For a small deployment, you install them in the same box. There are three main components that you have to put in the same place, and that's it. It is not really complex to set up. Zabbix isn't really geared like some of the other solutions where there are different modules for each part. Zabbix is monolithic. You have a core system that can do everything, and it is extended with the plugins that provide additional integration and monitoring, but the framework and the UI are in one package or software.

You definitely need someone to administer the platform after it is deployed. Otherwise, it is a bad deal. The number of people required for maintenance depends on the site. It can start with someone part-time, and it can end with two full-time persons developing scripts and plugins. Post-deployment maintenance also depends on the monitoring requirements. You can't have a monitoring solution that is central to your network and sees everything but doesn't change as your network changes. If your network changes, your solution has to adapt to it, which is normal for all monitoring solutions. Similarly, if you have too many metrics, you would require some database tuning as the solution gets bigger. 

It is open source. If you want to have a subscription or official support, you can pay for it. They have different plans, which are not that expensive. The plans are based on per monitoring server, not per monitored equipment. So, it is not at all expensive, and you can also live without the support if you want a cheaper option.

We evaluated different solutions in 2012 and  2017. We favor open-source solutions or open-core solutions that support open-source models. These open-core solutions are not open source, but they have an open model. They come with plugins. Such solutions are the best because they offer flexibility, and you can add your own monitoring on top of them. You can add your own plugins and extend a solution beyond its original capabilities. A proprietary solution such as SolarWinds is not that flexible because it is closed. You have to find a suitable plugin or module, but you can't really develop something on top of it. There is an SDK, but it is really hard to use. I've never rarely seen it used.

Zabbix is a solution we offer to answer some of the main customer monitoring requirements . The solution that we go for depends on the environment in which it will be used. We select one of these depending on a customer's environment and prerequisites. We see whether a customer's environment is really rich, and how many customized and standard applications a customer has. Zabbix also has more integrations with on-prem infrastructure and cloud solutions.

In comparison with Nagios and alike solutions, Zabbix is less fragmented providing better integrated components. They also invested in the last years quite a lot of development efforts to build new custom integrations.

I would advise others to know scripting and Linux administration. These are the prerequisites. If you don't know these, you either have to get better at them or get an expert to help you. After this solution is deployed, you should have someone to administer the platform. Do not leave the platform as it is. It should evolve with the network. Otherwise, it becomes irrelevant.

I would rate Zabbix a nine out of ten. It is a very good product, and it is for a good reason that we have chosen Zabbix as part of our monitoring portfolio.

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 needed a tool to know what the space inside of the infrastructure is like. My work was to use Zabbix to get information about the IT infrastructure in the village or in the towns that are very far from the headquarters. I had to use Zabbix to provide information with maps that the IT was working and so that the headquarters can see in real-time what the healyh of the IT infrastructure we had deployed in the electrical network is.

After this experience, I tried Zabbix in african organization based in my country and it was used to monitor the IT infrastructures in three countries, cameroon, benin and ivory coast. For the moment, Zabbix is not yet very popular here but I really appreciate it and really want to make people know that it's very simple to use. 

In 2023 i tried Zabbix 6.0 on Rocky Linux 9. And news features like pdf report have improved my Admin Sys routine.

Zabbix has improved the daily monitoring tasks by making them easier and faster.

The feature that I find most valuable is the stateful map. In fact, the Zabbix map designing tools permit to make monitoring stateful maps with topologies similar to the reals IT network maps.

My company wanted to do an exercise command to access IT from Cameroon. They wanted to access an FSS to a second host with second equipment that was on another coast but it is not possible on Zabbix to do it. They want to directly access from the front-end of Zabbix to access a prompt in Zabbix to an access terminal. In the front-end, there is no way to do that. That would be an important improvement. 

II have been using this product for nine years.

It is very scalable because I tried version 5. I used 5 from 0 and I see that they have improved many things, but there is not yet this option to have an access terminal where you have many functionalities. 

The scalability works fine because the community is very active. When a new version comes out, we can see that they have tried to add.

The technical support is very quick. When I have a problem and I post it in the community, they answer me very quickly. For now, i don't need any technical support. 

Positive

In fact, even if I have looked at Nagios first, before Zabbix I did not really use it or any other monitoring solution.

The initial setup was very quick. The first time it was long because I didn't know it yet. I was only using Windows. The first time was very difficult because of the operating system. 

I implement Zabbix in-house with as outsourcing offficials webs tutorials

Zabbix exploitation has dispensed with financing frequent visits to the technical area through alerts, notifications, and stateful maps. Thus, the return on investment is more than 100%.

Zabbix is an effective cheaper network monitoring solution because it doesn't need any ongoing cost due to licensing.

Before choosing Zabbix, we evaluated Nagios but we were not comfortable with notifications messages syntax and configurations.

I would recommend Zabbix to people who want to monitor a simple network.

I have found that the literature on the website is not very easy for some people. They want to be in those to read more about Zabbix, how to install it, and what the normal problems are.

I would rate it a nine out of ten. 

In my primary experience with this solution, Zabbix was used to monitor the IT infrastructures of a SCADA system in electrical substations. It was about network supervision of routers and switches that are used to communicate with electricity installations through RTU (Remote Terminal Unit).

Zabbix has improved the quality of monitoring because of the user-friendliness of its Graphical User Interface, so is easy to use even for non-IT employees.

Customizable network maps and email alerts or the intuitive web interface had made Zabbix very useful. 

I really enjoy network traffic triggers that allow us to check traffic threshold from ISP.

They should open an SSH session from the web interface, and options to design 3d map will be nice.

I have been using Zabbix for four years. I discovered this very efficient network monitoring tool in a course from my engineering training and stuck to it!

Zabbix is very stable monitoring solution. Indeed, one of my first zabbix server, 3.2 version on Centos 7, is still working fine today (seven years later) and without any needs of maintenance or upgrade.

The only Zabbix support that I use is Zabbix Telegram and Discord Community.

Positive

Zabbix was my first love for network monitoring and I just adopted it. I did not previously try a different solution.

The initial setup is very easy, with a few command lines. For simple network monitoring, there is no need to install any special packets on the Linux server.

My first installation was Zabbix 3.2 on a CentOS 7 Linux Server. The very difficulty that I faced was the fear of the unknown!

i implemented this solution through a very small in-house team where no one was a Linux expert.

Zabbix is open source and free. There are no hidden costs for any features or licensing. So, I would advise hat other s use this product.

When I was looking for the best solution for our monitoring needs, before choosing Zabbix, i had evaluated other tools options like Nagios.

With regards to COVID-19, Zabbix's meetup and training were 100% online and were very helpful for keeping in touch with network engineers around the world, despite social restrictions.