Zabbix Reviews

We are a solution provider and Zabbix is one of the products that we implement for our clients. I am the senior consultant for Zabbix in my organization.

The use cases are pretty basic. They include memory and disk monitoring, database monitoring, log file monitoring, and application monitoring.

The most valuable feature is the trigger dependencies.

The documentation is good.

Zabbix has a roadmap and they are continuously and frequently adding new features. Most of the features are good.

The reports are not great and should be improved. In other tools, we can schedule reports and fetch them. However, with Zabbix, we cannot export reports. It is possible to export some of the data but our monthly reports, including those for performance and availability, cannot be exported.

This product is not highly available by default. I have read that in the next major version, 6.0, they are planning to do that for the proxies.

I have been working with Zabbix for between three and four years.

This is a very stable product.

This solution is scalable and I have no issues with it in that regard. We have five to six people that use it. They primarily do admin work.

There are two or three who architect and design solutions. We add and manage servers, as well as perform maintenance.

We do not have a Zabbix technical support subscription. We manage it ourselves.

The blogs that are available online are okay.

There are a few problems but if they fix them, then Zabbix is a very good tool compared to others. This includes tools that you have to pay for.

The initial setup for the Zabbix server is pretty straightforward. 

Initially, it was just a single node, so the deployment didn't take long.

This is an open-source solution that can be used free of charge. Support is something that you have to pay extra for.

My advice for anybody who is implementing Zabbix is to read the documentation and go through the use cases before beginning the implementation. Many use cases are available online.

I would rate this solution an eight 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've designed and built a high-available solution with Zabbix version 5. I introduced and deployed Zabbix in my current company, and it ended up becoming a production service within the company.

I like being able to use proxy servers for different locations. The agents are pretty cool. They're easy to roll out. 

The standard out-of-the-box templates are also pretty easy to use. The integration with other learning products is also good. I have, in the past, used Slack, but we've integrated it with Microsoft Teams. We also use it for SMS with a service called Redcoat. It is very flexible.

It does what I need it to do, and my manager is very happy because it doesn't cost anything. We are nearing 4,000 hosts inside Zabbix, and we've got another 6,000 access points to add to it. We've thrown everything at it, and it has managed to keep going. I am very impressed with the tool, and I'd shake their hand very hard if I got to say the compliments to the Zabbix team. They keep improving it and doing refreshes, which is one good thing about it. There is also online information as well as books that you can purchase if you're willing to read enough. There is a lot to pick up, but it is a pretty complete solution.

The APM monitoring has room for improvement, although I hear that the new 5.2 version has some improvements in that area, and I'd like to give that a go. I would like to see a few more templates out there for different styles of monitoring. I use the Grafana interface for reporting. 

I would also like it to have an out-of-the-box ability to email reports. You can create reports, but to be able to email those reports would be really helpful. I've got users who are not interested in logging in and generating a report. They want it all pre-canned and sent to an email address. It would also be really handy if we could pin certain reports up onto platforms such as Teams or SharePoint.

A GUI for the proxy server would be cool to have for debugging purposes and for the support teams to have a look at, but I don't know whether that's really feasible to do. I get enough from the log files themselves.

I've been using this solution for probably over five years. I started using it from version 3. 

Zabbix is very stable. We ran into a few performance issues in the early proof of concept days. The database running on normal hard drives impacted the ability to process all items in a timely manner, and when I moved to SSDs, those issues went away.

For all implementations, the sizing calculator needs to be used to ensure the correct size of the database. Based on the number of hosts and items the performance of the database needs to be factored in.

We've managed to scale up recently from about 150,000 items. We're now on to about 380,000 items. We're not really seeing any major flaws or issues in that environment. It is pretty good.

Many years ago, when I worked for a different company, I had access to their support, and they were very good. They were very knowledgeable. I was working on versions 3 and 4. I also got training from them. They did a five-day training course for us. 

I am pushing my company at the moment to try and get an enterprise license so that we can get some on-site support and some guidance to make sure that we're deploying within recommendations and the way they would do it. At the moment, they're relying on me to get it up and running and make it work, but I'd love to have some support, and I know they're very good. It is an education company, and I am keen to get more people in front of it. There'll be more opportunities within the university itself from what we've already done, but that's a work in progress.

I've done many setups. They're all pretty easy to do. There are lots of different flavors of it. I've used Apache and Nginx. MySQL and PostgresSQL are the two databases I've tried out. I've done different versions. 

At the moment, my system runs on Postgres. We're looking to implement TimescaleDB on that, and we've got an Ingenex front-end that we use. It is a little bit more solid than the Apache version, and it is very flexible. You choose what you want and then you roll with it.

My manager is very happy because it doesn't cost anything.

I would definitely recommend it. It is very good for what I want it to do. I would recommend getting your Linux and databases teams involved very early on in the journey, and when you are deploying, make sure that you are targeting the more important applications in your portfolio. Don't just try and deploy it on everything straight off the bat. Try and pick some critical applications to look at and build the value in the product in the initial phase, and that usually gets people interested in the application and moving forward. That would be my advice to people. One of my drawbacks was that I waited a bit too long, and when I brought them on board, I had already built most of the environment myself. I should have got them involved a lot earlier and sooner. It is not really a bad thing, but you can't do everything yourself, so try and get people on board.

I would rate Zabbix a nine out of ten. I am pretty biased. I really enjoy using Zabbix, and I feel it does what I need it to do. It definitely ticked the boxes. In my current role and in three years, I've gone from demoing Zabbix, doing a proof of concept, and integrating it with a few things to the boss turning around and saying, "Right, make it production." I have to admit that everybody that has come into contact with it or I've presented it to has been very pleased with the results. It has been a very good fit. I can only compliment the tool. 

I am not giving it ten because it's not perfect. I don't think any monitoring tool is absolutely a hundred percent perfect. There is always room for improvement, but this has to be one of the better ones. I know what I'm doing, and I could do more if I had support from them, but what you can do with the tool is very good as compared to other tools that I've tried out in the past, such as Nagios. With Nagios, if you really want the full functionality, you have to pay for it. Here, they give you that functionality. You've just got to know how to use it. It is very clever, and it has definitely won me over as a tool. Thanks to deploying and using Zabbix, I have learned a lot of stuff around Zabbix as well. I have learned a lot about different tools such as Linux,  MySQL, and Postgres that are needed to run the service. It has been good. I have enjoyed it a lot.

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.

We use the solution for network monitoring and status monitoring.

The calculations part is the most valuable. 

Improvement is needed as per customer requirements.

I have been using Zabbix for some time. 

It is a stable solution. 

The scalability is nine out of ten. It is recommended for medium enterprises. 

The initial setup is straightforward. The deployment takes two to three years. 

Overall, I would rate the solution a nine point five out of ten. 

Our customers like Zabbix because it's an open-source tool, but integration with other tools is not that easy. The company that I work for employs talented people and a good integration team who can get the end-to-end implementation and integration done properly. 

Zabbix is basically network monitoring software. Often, we are working with various solutions that we are attempting to integrate with Zabbix, and at the same time, we're trying to integrate a couple of bots to take automation to the next level. 

We have been able to address all the monitoring challenges with Zabbix , which is in addressing all the concerns from the customers

Because Zabbix is an open-source tool, it makes it much easier for us to provide the customizations that customers want nowadays. The best thing about Zabbix is the integration and the speed of the included APIs, that's the beauty of this product. It's an enterprise-level tool that allows you to monitor it with a number of devices and hosts. The integration capabilities and APIs are the best part.

Currently, we're looking for more AI and ML related capabilities, which is missing from Zabbix at this point in time. There are tools out there with plenty of AI and ML capabilities and this is something that Zabbix needs to come out with. That would make this a great solution to sell. Essentially, they are trying to achieve automation by introducing external RP bots. If Zabbix could fix this issue, it would be a fabulous solution for us to sell and for companies to use.  

We have been using this solution for three years.

Currently, we have a support agreement with technical support, and we're happy with it. We have taken up a paid service on support models with them as a partner, but lately, our own developers have been solving any issues. So, for slightly over six months, we have not contacted Zabbit for support. 

Positive

The setup was free and because we use multiple tools, it was very easy for us. We had some teething issues, but the community is very good and helped us with that. The Zabbix community is very reliable and is quick to supply you with information when needed. 
The online support that we received from the community was very good and the KD was good enough for us to get it deployed. We didn't experience many challenges because we already had some concrete knowledge surrounding it. 

Deployment depends on the setup; I believe we had it installed in two days. Our customization depended on what level we were taking it to. We did all of the integrations and customizations ourselves, as required, but I believe we finished the base implementation within two days.

We have about 10 engineers, three to four of whom are certified on Zabbix and they take care of all maintenance related issues.  

I would recommend this solution to anyone interested in enterprise-level monitoring and integration. The only improvement I would suggest revolves around its AI and ML capabilities. Those are the only problems, at this point in time, that I see with this solution. If these issues are addressed and included in a future release, then this will be an end-to-end, fabulous product for monitoring and automation.

Overall, on a scale from one to ten, I would give Zabbix a rating of nine, simply because the world is rapidly progressing toward an AI and ML environment. Whenever you check out a new product, from Moonsoft for example, most of the marketplace jargon revolves around AI. So, when we talk about AI, the customers are ready to just blindly buy the product without understanding if it is real AI and ML, truly capable of completing the task at hand. That's why we started using bots to automate steps; to show the customers that even Zabbix, as a solution, can be used for automation using bots. It's a tedious process, but it's a great method of comparison.  

We use Zabbix to monitor our physical, virtual, and network infrastructure.

Zabbix is our primary infrastructure monitoring and alerting tool. Thanks to Zabbix metrics we are not just notified of failures, but we have enough data for preventive maintenance optimization and capacity planning of our compute infrastructure.

The low-level discovery feature that lets us auto-configure the monitoring for various systems is a valuable feature.

The option for multiple monitoring protocols - we are using the native agent and SNMP - is valuable.

The flexibility to view and log the data history is valuable.

We can create custom metrics easily using the Zabbix sender utility. 

The quality of the templates (typically offered by third parties) is often poor, and they contain bugs. I encourage the Zabbix users to understand the template structure to be able to improve them.

The setup process for certain integrations can be challenging and there is potential for them to be improved or at least better documented.

The creation of custom metrics could be simplified.

Zabbix can use better documentation and support for troubleshooting.

I have been using Zabbix for two years.

Zabbix is very stable.

Zabbix meets our needs well for our small infrastructure of about 40 physical and 60 virtual systems.

We only used the product documentation, which could be better.

Zabbix was our first choice for infrastructure monitoring. We are using Prometheus/Grafana stack for metrics from other environments.

The setup process has a steep learning curve. The documentation provided lacks detail, and I encountered some difficulties during the integration steps. It took me a few hours to set up the database.

We implemented Zabbix ourselves. We are an experienced IT team, though.

Zabbix is free, open source software. 

I give Zabbix an eight out of ten.

Choose the templates to use carefully. Get to know the Zabbix templates and be prepared to modify/fix them because the templates available from the Internet are often buggy or incomplete.