Zabbix Reviews

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.

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.

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.

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 monitor Zabbix for different clients. In total, there are less than 40 users, using this solution. 

We definitely plan to increase usage and continue using Zabbix.

I have been using this solution for the past few months. 

It hasn't really been that stable, but I think that has a lot to do with the specs. It could be more stable.

Zabbix is scalable.

I would absolutely recommend Zabbix to others. Overall, on a scale from one to ten, I would give Zabbix a rating of eight. Once I have more experience with it, maybe I'll give it a higher rating. 

We - msp - use this solution for enterprise-wide monitoring and alerting for network devices, appliances, Linux, Windows, Exadata, ODAs, Oracle, PostgreSQL, SQL Server, and MySQL databases.

We detect problems before the customer does and before it actually happens using the predictive functions in Zabbix. Zabbix gives us a single point of truth.

The most valuable features are the low-level discovery, auto registration, host discovery, integration with other tools, and the zbxdb plugin for database monitoring

Very good templates

I would like to see a more flexible mobile client, and better HA out of the box.

It would also be very interesting to have a GUI on the proxy server[s]

I have been using this solution for eight years.

Stability of the product (servers and agents) was one of the key factors we checked. The agents normally have a low footprint and are very resource friendly.

Especially when using postgres with the timescaleDB option, the performance improved a lot because data deletion is now done by dropping partitions, which saves lot's of database time. We are confident that zabbix kan keep working for us while we grow. In the end, the bottle neck will be the database but we see a lot of options to stretch this.

Zabbix support works through various channels and works responsive. We are also very glad with the community support where we also share our experiences. Currently there is an active community in Telegram https://t.me/ZabbixTech

Earlier we used all kinds of other tools, all for a part of the stack. Oracle enterprise manager for oracle databases, PEM for postgres databases, SCOM for Windows, prtg for network, appman for applications. This required to run and maintain all those tools .... Now consolidating to 1 saves a lot of time and gives a single point of truth.

The initial setup is easy. Making it completely HA required some work but if you are familiar with the redhat tools it is not hard.

We implemented the zabbix solution our selves. A team consisting of a Linux admin and a postgres dba that both know Linux and zabbix setup the infra structure. The other teams gave input for their metrics, thresholds and views.

Combined with the other tools that we phased out the ROI will be within 1 year. One of the things we save a lot of money on is the replacement of SMS by an other notification service.

Make a POC, start simple and let it grow. The servers are created with good performance by design. Memory for the caching, both on the database as on the zabbix server are important. As database backend choose postgres with timescaleDB. This save many hours housekeeping processing. For proxies, sqlite will do nicely. Involve a dba for the database setup.

We checked the above mentioned options. Zabbix came out as a winner. Simple, good web application, no need for fat clients which makes maintenance simpler. Zabbix does not have the nicest GUI, compared with some above but it is certainly acceptable, especially when pricing is taking into account. Especially with the postgres database in combination with the timescaleDB options is has an excellent performance. It has a clean database design and handling.

If state of the art reporting is important, integrate with grafana. It can be done via the api and directly on the zabbix database.

If performance and scalability is important, use postgres with timescaleDB as database backend. This wins hands down compared to mysql.

I primarily use this solution in some of our different monitoring systems, including our different servers, and applications. We use it for the maintenance of the main server in the laboratory.

The ability to connect with monitoring is very useful for us. It's great that we can monitor different applications. We can even monitor remotely.

I recently tested the solution's ability to hold up to rebooting machines remotely and we were able to do so with ease. 

There are lots of great features and functionality within the solution.

So far, we've found the solution to be quite stable.

The product has a large community and therefore has lots of documentation around various aspects of the product.

I don't recall coming across missing features. It's a fairly complete solution.

The user interface could be a bit better. They could update it a bit.

The solution offers very good stability. It doesn't have bugs or glitches and it doesn't crash or freeze on us. It's been reliable from the very start.

I have never tried to scale the solution. I can't speak to its level of scalability.

However, it is my hope that it is. It's important to be able to scale it.

We only currently have 10 people on the solution. It's a small group and therefore we haven't yet had a need to expand it.

While I haven't ever actually reached out to technical support, I'd say that it would important to have access. If there was a question the community couldn't answer it would be nice to know if we could turn to Zabbix directly for assistance. 

We did previously use a different solution prior to Zabbix. It was a suite of applications that included, for example, DLP and myShell. I haven't used it in a very long time, so I can't speak too much about my experience with it or how it compares.

The initial setup isn't overly complex. It's largely straightforward.

There's also a fairly sizable community around the solution and there's just so much documentation and insights from other users you have access to, therefore it's very easy to find answers to your questions when it comes to implementation.

We use a free community version of the solution. We don't have to pay for licensing. 

I'm not really a user. I deploy the solution.

Overall, I would rate the solution at an eight out of ten.

I use Zabbix on my Raspberry Pi and it is set up to monitor our network. We are testing it at the moment to see how it responds to our network, which includes laptops and workstations.

I have not gone into great detail with the product, although I expect to be doing that within the next months.

It is not hard to integrate.

I am having difficulties connecting it to Grafana, as well as some of the other plugins like Kibana. 

I have been using Zabbix for the past year.

The stability is okay, although, at this point, I'm only using it on a Raspberry Pi. I need to set it on a higher level server to see exactly how it responds on the network and how to deal with it. In this testing phase, it is stable, but when I'm ready to put it live into production then we will see how it reacts.

I haven't tried to scale it, yet. I am the only one using it because I'm performing the testing.

I have not been in contact with technical support.

The basic setup is very easy. I installed it in a Raspberry Pi with a Linux version. It took perhaps 20 minutes to install, at the most.

This is a product I can recommend to others.

Overall, I think that this is a great tool, although I need to spend more time with it to see exactly what the different features are, and how I can use it to implement my network better. There are a few glitches that need to be fixed, such as making the plugins easier to install.

I would rate this solution a nine out of ten.

We have two Zabbix servers, deployed locally and in our New York datacenter, and we use them for monitoring traffic. It is an order processing system and we need to schedule and monitor our infrastructure.

Zabbix is very easy to implement.

The interface is customizable, so we can create the dashboard that we need.

We need to set it up step by step in order to ensure that it is stable and works properly.

If you want to use all of the features then you have to pay a licensing fee.

I have been using Zabbix for approximately one year.

We use Zabbix on a daily basis and we haven't had any issues with stability.

We have not needed to expand it because our infrastructure is very small. It includes a server and some VMs.

When we have a problem, we search the web site for how to resolve it. We have never had an issue that necessitated contacting technical support.

In my last job, I worked with Nagios. I found that Zabbix is a good system for monitoring and it is easier to implement, and it is also less expensive.

The initial setup is easy to do. It involves implementing agents in the server, but it is not difficult.

We implemented it with our in-house team that is also responsible for maintenance. This includes updates to the product. There is a team of three administrators who manage it.

Zabbix is free but if you use it in production then you have to pay for it. It is not expensive if you compare it to something like the Amazon monitoring system.

Also, it is an open-source product, although some features are available at an extra cost.

Overall, this is a great tool and I recommend it.

I would rate this solution a ten out of ten.

We are using Zabbix for monitoring our servers and to display network traffic.

The most valuable feature is network traffic monitoring.

When we have a problem, we have to do a lot of research to solve it.

I have been using Zabbix for a year and a half.

This product is quite stable.

We have not had to contact technical support.

The initial setup is not complex. In fact, it's quite easy.

It was quite quick to deploy.

We have our own team who installed it and know how it is used.

This solution is completely open-source, so it is quite affordable.

I would rate this solution a seven out of ten.

Primarily we are using an on-premise installation, and just now we are exploring the cloud installation. It's basically the same one. It's a pre-production and production environment. We use the on-premises for testing, and we have the one with the cloud installation also.

We are using this solution for monitoring our internal network and infrastructure in the company, and also for monitoring a couple of our customers' installations. Not only their network but also their services, and to reduce consumption.

The graphical user interface could be customized a little bit more, and also the dashboard could be more friendly.

I would like to recommend the possibility of being integrated for the monitoring of the Micro Strategy System environment and clusters of machine Micro Services.

I have been using Zabbix for perhaps six months

This solution is stable.

It's a scalable product. We have 20 users in our organization who are using it.

We don't have any experience with technical support. We haven't had any reason to contact them because we have been able to address any issues on our side.

The initial setup was not complex. It took two hours to install.

My colleague, along with one other internal team member deployed this solution. We did not use anyone externally.

We have only just started using this solution a couple of months ago, but we plan to continue using it in the future.

I can recommend this product to others who are interested in using it.

I would rate this solution an eight out of ten.

The primary use case is the cost. Typically speaking, our customers have a plethora of tools and they find it very difficult to manage their business services with a selection of tools. In most cases, they're able to replace all of their tools with one — Zabbix. 

We counsel groups and we recommend using Zabbix — we're a reseller.

We focus on Zabbix. When a customer needs it integrated with Microsoft, or ServiceNow, or other solutions, then we help them out from a consulting perspective. We focus on and we recommend Zabbix. Which is an enterprise monitoring solution.

I take care of sales and marketing.

If the customer requires integration, then there are easy ways of integrating Zabbix with JIRA, ServiceNow, ITSM, and all other sorts of different solutions.

The most valuable aspect of this solution is the fact that it is enterprise-level, scalable, and free.

Just being free isn't enough, obviously. You have to be able to respond to a considerable number of enterprise requirements and be secure. Security is part of the enterprise requirements. The fact that Zabbix can offer those things, and it's free, is why our customers choose it.

When our customers don't choose to go with Zabbix, it's usually been because they're looking for a solution that also contains mainstream AI, AIOps, if you wish. AIOps is a fully noted marketing buzzword, which can mean all sorts of things for different people. When I use that term, I'm talking about the requirement to analyze in-depth enterprise data. Zabbix is not an analytics platform.

We've never had any issue at all integrating Zabbix with any of the existing enterprise tools, whether it be ITSM, JIRA, or an analytics tool like Splunk — it's never been an issue. Their design team does a very good job allowing people to get access to the Zabbix database and to the Zabbix Schema, which defines the data that's stored in.

In the latest version, which is just about to be deployed, they are adding the capability of doing APM (Application Performance Monitoring). That's a feature that has currently been lacking — we'll have to see how it goes.

I have been using Zabbix for one year.

It's a very reliable platform and we've never had any issues regarding the scalability or the stability of Zabbix. We've seen customers (not our customers) that have got huge implementations of millions of objects which are being managed. We've never had any issues with scalability.

Zabbix is not a licensed software. People don't buy licenses for Zabbix. Technically, we are a reseller. So what is it that we resell from Zabbix? The answer is their service. Either their contractual support, their annuity based support, or their technical support. We can get them involved in certain implementations if the customer requirements require that.

Zabbix technical support is sold separately.

The initial setup is straightforward. It's a powerful tool; it's applicable to many different domains, through networks, through infrastructure, through applications, through containers, virtual resources, and cloud-based applications — it can be applied to all of them. The initial implementation is usually something we never have an issue with. It's a very easy-to-download package. Implementation requires experience. Deploying Zabbix is very easy, but if you don't know what you're doing, you can make an awful mess. That's where and why we offer our consultancy — to help people to make sure that they don't end up with petabytes of monitoring information on the first day. Which of course no one has any time to go through and handle. 

Speak to a Zabbix expert before you get started because there are so many options in terms of architecture for deployment that you really need to understand relating to how Zabbix can give you those options and why they're useful. Options might include encryption or distributed architecture, so delegating monitoring responsibilities close to the objects that have been managed using proxies is a good idea. There are choices to be made so if you don't know the product and you are speaking to someone who does, then listen, because they can advise you properly to get the best benefit out of the software. Zabbix is a free package, you're not paying for any licensed software; the expense of Zabbix over time is related to how it's deployed and used. If you don't deploy it right, then you'll spend more time fixing your mistakes than actually using the software.

On a scale from one to ten, I would give Zabbix a rating of eight.

I am not giving them a higher rating because they don't have analytics. They're getting there. They're becoming more and more proactive. They just added something which was very important called 'application performance monitoring'. From an enterprise perspective, they still lack the analytics capabilities, but that's not necessarily an issue unless you're looking to choose one tool that does everything.

The primary use case is to resolve connection issues for my YouTube access.

I am still exploring all of the features that this solution offers. At this time, I have only downloaded the system log and scripts. 

During my testing, the features that I like the most are that it can be integrated with my system, and it provides me with reports of all of my servers. This allows me to know what is going on with my servers.

Also, I can create a script to download all of my configurations.

I don't know if I can remotely restart my servers or to know how a guest is doing on the server. I would like to remotely connect to the computer, and Zabbix doesn't have this capability. 

I have to use another software such as Emperor to log into the computer to see what is going on with the servers.

I would like to see a RAS integrated with Zabbix for monitoring, also to be able to check the server and to have an automatic display to do what we need to do.

We are in the testing phases of Zabbix. I have been testing it for three months.

We are currently deploying it on my VMware to test the product and see how it works. Once I have all of the skills and requirements, I can process it into a real deployment.

Zabbix is a stable solution.

I am currently the only user in my organization.

I plan to use Zabbix in the future, as it has helped me resolve my connection issue.

I have not contacted technical support. When I have an issue, I research their YouTube channel and watch their videos. 

You have to be patient. It helped to resolve the issues.

Previously, I was using the PRTG Network Monitor. It's an expensive solution. 

I chose Zabbix because it's a free edition, and I don't require a lot of monitoring. Also, I was limited.

The initial setup was fine, it was simple.

For a proper installation, it can take up to two weeks.

I completed the installation myself.

I installed the server, and then the client on the Windows machine to make the link.

It's an open-source solution that can be used free of charge.

I have not tested any other solutions. I looked at most of the other products, but we have to pay for them. 

To resolve a fixed problem, I would have asked the management to purchase the product, which would take time. Instead, I read the review and installed Zabbix directly to resolve my connection issue.

I am also using this solution to help me with writing my master examination. I need to write something about this solution.

I would recommend this product to anyone who is interested in using it.

I would rate Zabbix an eight out of ten.

We primarily use Zabbix for monitoring our infrastructure.

The most valuable feature is monitoring.

Having a more customizable interface and dashboard would be an improvement.

The interface could be more user-friendly because it is can be really complicated if an end-user has to configure it. The administrator usually has to take care of that.

I would like to see more SNMP and storage support.

Application monitoring should be included in the future. I would like to see voice telephony monitoring and database monitoring.

The reporting functionality is limited.

I have been working with Zabbix for the past four years.

This is a stable product.

We have had no problem with scalability. The only people who use it are the IT staff, which is between 10 and 12 people.

As we are using the free version, we do not have a support contract.

We are using the free, open-source version.

This is not a product that I recommend. Instead, I recommend using SolarWindows or ManageEngine for monitoring because there are more features on Zabbix with limited usability. Reports are also limited. Basically, you get more features in SolarWinds or ManageEngine.

I would rate this solution a five out of ten.

The solution can be used to monitor both on-premises and cloud infrastructure.

The flexible licensing model is one of the solution's most valuable aspects. It really allows for great flexibility for companies.

The initial setup is very straightforward.

The NetFlow integration really could be improved upon. In general, integration with other solutions and services needs to be worked on.

The documentation could be improved. I find that it's a bit limited.

It runs on a Linux backend, and we're using it to monitor our Windows platforms. For people who are not familiar with Linux, there may be issues. You do need to have a bit of Linux knowledge before beginning, otherwise, you may have problems working with it.

We've been using the solution for two months at this point. It hasn't been a very long period of time.

The stability of the solution is good. It's reliable. There aren't glitches or bugs. It doesn't crash or freeze. We haven't had any issues.

The scalability is quite good. If you need to scale the solution up, you can do so. It's pretty straightforward. We haven't had any issues so far.

In our organization, we have about 1,600 users on the product.

We most likely will increase usage in the future.

We've used technical support in the past. They have different platforms that handle requests at different levels. The gold platform, for example, offers support but is slightly limited. 

The initial setup isn't complex at all. It was very straightforward.

In terms of deployment, it takes about a day, however, you have to add in all the other items that you're monitoring. We deployed everything and then rolled it out over the course of a couple of weeks.

I handled the implementation myself. I didn't need to solicit the help of a vendor, consultant, or integrator. 

The licensing is great on Zabbix. It's very flexible and great for various types of businesses.

We're just a customer. We don't have a business relationship with Zabbix.

I'd recommend the solution. It's easy to use and it's been quite useful. New users do have to be pretty comfortable with Linux, however, otherwise, they may have a hard time adapting to the system.

I'd rate the solution eight out of ten overall.

Monitoring systems and services that don't have their own solution in our environment. Single place to monitor multiple systems and processes. We monitor servers, websites, key card devices, etc..

Before we didn't really have a centrally managed monitoring solution, so adding this product has been a blessing as we are able to actively monitor and react accordingly. Being able to monitor almost any device in one location is extremely convenient.

The feature which I like the most would have to be the GUI. At first, I was put off, as I felt it was too complex or busy. Upon using it to setup devices, I found it was well laid out and has come a long way.

The agents are also very easy to install and manage, making this more of a turnkey solution for most.

I wish it had more options for personalizing the product, such as being able to include your company's logo without editing text files. More templates for specific devices.

More than three years.

None yet. Runs solid on very light resources.

Not yet, but as of now, it's a single server - might have to dive in at some point with the proxy configuration.

I have used publicly available resources. I can't comment on their customer service.

We used Cacti, which worked well for our uses. We moved because we needed a more updated solution that had support for a myriad of devices. The community is also active in development of plugins.

It's a decently complex system to get setup, it's not a simple package based system (well technically it is, but not as easy as others). It's also not as extreme as Nagios or Prometheus. We added Grafana, which made it a little more complex.

In-house team.

Time and knowledge. Without it, we wouldn't have known of current issues in our environments. It allows us to deep dive and get to the core issues quicker.

It's open source, so no cost/licensing needed.

Nagios, Prometheus, Check_MK, Adagios, Icinga 2, Zenoss, PRTG, and Cacti.

Zabbix coupled with Grafana (there's a plugin for Zabbix, very easy to setup), is a great monitoring stack. Leveraging "Let's Encrypt for SSL" is also a must!

I implement Zabbix for large companies with over 5,000 employees.

In the near future, we are going to see integration with its cloud platform.

We would like to use it for RBI, for service and credibility reports for our manager and management staff, and we also hope to use it to deliver customer scripts, etc. Currently, because we monitor over 5,000 hosts and servers, we need to use open source. 

I have used Zabbix for the last five years.

Zabbix is both stable and scalable. As I mentioned earlier, we scale more than 5,000 hosts.

Currently, our own team provides support, but in the future, we may use Zabbix support.

We also use Nagios, but we are going to stop using this solution as it has specific limitations that we require. 

For us, the initial setup was complex. We plan on integrating Zabbix with Prometheus and Grafana for a smooth relationship between dashboards. 

We purchased Zabbix for a good price, including support. It's cheaper than Datadog and ScienceLogic.

On a scale from one to ten, I would give Zabbix a rating of nine, strictly because we would like to see better integration with mobile TeleCloud.

I was using Zabbix as a monitoring tool at my previous job, although I have left that company and am no longer using this type of product. We were using it for monitoring routers and a few thousand other devices. We had visibility as to their status.

The most valuable feature is the alert and alarm monitoring.

If Zabbix had a better dashboard then it would be nice.

I had been working with Zabbix for three years.

The stability is very good.

We had between 20 and 30 users and more than 2,000 devices.

I have not personally been in contact with technical support.

Prior to using Zabbix, we used Nagios. We switched because it became unstable and clumsy when we grew to have more than 2,000 devices. Zabbix was much better in terms of scalability.

I don't recall all of the details related to the initial setup, although I remember that it was not quite easy. We had to conduct quite a few searches on Google during the process in order to properly understand how to install it. If I remember correctly, there were a couple of errors.

We had two engineers who were responsible for maintenance.

Overall, I think that Zabbix is an awesome tool and I would use it again, rather than another one. For us, Nagios was a disaster and Zabbix was the savior. We didn't require any functionality that it didn't already have. My only complaint is that the dashboard needs to be improved.

I would rate this solution an eight out of ten.

Our company works with the health ministry in our country. We implement the solution for them and they use it as a monitoring solution in order to watch trends and server patterns, etc.

The solution works well for monitoring our on-site server.

Sometimes, the server can go down. When this happens, the solution has the capability to alert us to problems and will automatically notify us of any issues via email.

The implementation process is very straightforward.

The server monitoring could be better.

I'm not well versed in Zabbix, so it's difficult for someone like me to handle the setup. They should work to make the implementation much easier. It would improve the useability of the solution.

The solution needs to have a higher quality of performance. Performance is very important to our clients, and this solution doesn't perform very well. The quality and code are difficult.

The solution does not scale well.

We've been using the solution for one year.

HIgh performance is important to us, and this solution just doesn't offer it. It's unreliable. The quality just isn't there right now.

Our company needs a solution that can scale, and this product does not offer good scalability. It's one of its biggest downsides. If a company needs to expand the solution, they'll find that they won't be able to effectively.

We haven't had any issues with technical support. They've satisfied our needs to far. We don't have any complaints about the service they offer their clients.

The initial setup isn't too complex. It's fairly easy to implement and set up.

We're just a Zabbix user. We don't have a special relationship with the company.

I would rate the solution three out of ten. I would rate it higher if there was better scalability potential and the performance was of a much higher quality. 

This is a network monitoring solution that I was playing around with to see if it would meet my needs.

Zabbix helped me to identify issues on the system, as well as ports that were open.

The most valuable feature is the support for monitoring Cisco switches. It is easy to use because there is a free template for it included.

The main problem with Zabbix is that you have to spend time writing templates for all of the products that you have. It would work great if I had the time to do it, but considering that I have all kinds of different devices, I don't want to spend the time doing it.

If they included more prebuilt templates of devices that are in use today, then it would be very helpful. For example, they have a template for a SonicWall 3600, but they don't have one for a SonicWall Tz300. They do have some base templates but they are not customized for these specific products. For some products, I was able to download one, but not for all of them.

The documentation needs to be improved.

The deployment is complex and should be simpler to complete.

I have been using Zabbix for about a month.

Once the product is started, it is stable.

I didn't really test the scalability. For me, it wasn't scalable because I only used it for the devices for which I had templates. I was the only person who was using it.

I did not contact technical support.

I was using Kaseya Traverse, which I bought because I have a large Kaseya installation. I thought that it would monitor sFlow, but it didn't, so I returned it and then replaced it with LogicMonitor.

Basically, the problem was that in order to support sFlow, I would have to have a virtual machine for each of the network switches that I wanted to monitor. So if I had 50 switches then I would need 50 virtual machines to monitor sFlow. When they told me that it supports sFlow, then technically, they are correct. However, what they didn't tell me was that for each switch, you have to create a separate collector, which didn't make any sense.

With SolarWinds NetFlow, you can have multiple switches with one collector.

After I downloaded Zabbix, it was a pain to set up. I would say that it is complex in terms of the instructions. I was getting errors, and apparently, I was not the only one. I had to look at two or three different websites to get it set up. I found that if you follow the steps that come with it, which were not very detailed, it did not work. I had to search through different forums in order to figure out the error that I was getting. By the time I had finished, it took me three or four hours to figure out why I was getting the errors, and I had to reinstall it four times in the process.

In total, I would say that the deployment took at least 12 hours.

I completed the deployment myself.

I was using the free, Community Edition.

My advice for anybody who is implementing Zabbix is to seek the help of somebody who has actually done it before. Otherwise, it's not worth their time. Also, find somebody who can provide you with the templates that you need, or who's got familiarity with building them. It is a good solution if you have the time to build the templates and figure it all out. This requires knowledge of SNMP, as well as all of the devices. Then, you have to put it into XML and create a template that Zabbix can use. It is not a straightforward solution.

The reason that I stopped using Zabbix and bought LogicMonitor is not that it didn't work well. Rather, I needed a solution that was complete, where I didn't have to do the development.

I would rate this solution a four out of ten.

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.

• Multi-level infrastructure maps. You can set up highly customizable maps of your infrastructure, including each component status, maps which can contain submaps, and if something’s wrong at the submap level - the submap will be shown with problems.
• Agent and agentless monitoring. Installing an agent is the easiest way, but SSH, SNMP, Impi, custom scripting and other protocols are supported.
• Templates. There are a broad set of templates that define monitoring items for common OS and applications, you can build your own or use one developed by the community.
• An API for you to create, modify, and delete most things programmatically, including items, triggers, charts, etc.

As we know how are systems are supposed to work, Zabbix has given us the flexibility of building our checks without relying on special plugins. If some monitoring item is not provided already, building your own is very easy, and any scripting language will do. We’re able to pinpoint with accuracy where issues lie, and respond to them in a cost effective way, due to the nature of it being open source, with fairly decent documentation and optional commercial support.

The Java gateway for monitoring Java applications didn’t work for us. Our JMX Service URL’s are somewhat complex, but we were able to write our own JMX checks.

Three years.

When your checks grow to a certain volume, you need to adjust some settings on the server related to cache sizes, preforked workers, and so on. This is expected as with any service that grows beyond its default settings, there’s documentation about it.

The system is as scalable as your database is. We applied partitioning on the biggest tables to keep the performant at 14 new values per second. You can setup a distributed architecture consisting of an N number of proxies capturing data and reporting to N master servers.

Fortunately, we’ve never needed it, because we have very talented engineers in our team and there’s plenty of documentation available online. There are also user forums which are helpful most of the time.

A fork of Nagios called Icinga, it’s pretty good, but something like the Zabbix Maps feature was a must have for us. We needed something very schematic and flexible to show the overall status of our systems.

It wasn’t complex, but we have very skilled engineers.

The quickest way to go is to have a turnkey virtual instance tailored to your needs by Zabbix, or use one of the freely available ones.

The product is open source with optional commercial support, which is recommended to reduce the learning curve, avoid pitfalls, and keep the project going.

SolarWinds. Nice product, but our particular project was more in line with the Linux, PostgreSQL, and the Open Source philosophy.

If you’re into the Open Source and freedom principles, don’t mind getting your hands dirty, and have the technical skills, Zabbix is a good choice. Commercial support is available if you don’t want to go at it alone, lack sufficient technical skills, and you need help to keep the project going.

Highly adaptable to almost any environment and technology. The use of features, like Low Level Discovery, Templates, and Macros, allow an easy and customizable deployment over large environments.

Regarding notifications, the ability to use different media types and custom scripts gives Zabbix virtually no limits (mail, SMS, Telegram, Slack, etc.). Integration with other Open Source solutions, like Grafana, expand the possibilities for data visualization.

Availability problems are easily detected, minimizing downtime. Performance problems are detected before having an impact in customer experience. There is a centralized view of the whole IT system (HW to apps), and new devices services are easily integrated.

Reporting and SLA customization.

Five years.

None.

None.

None.

We are partners, so customer service does not apply to us.

We are partners with Zabbix. The response whenever we needed their technical assistance was excellent.

We used Cacti for data visualization. We switched because of the benefits of using Zabbix as a central monitoring solution instead of having multiple tools to manage.

Straightforward. Documentation on the initial setup is available at Zabbix's website and easy to follow.

We are Zabbix's partners.

Being truly Open Source, the only investment is in the time needed to get to know Zabbix and all the features it brings. This time is later gained in downtime minimization, easy scalability, and overall system status visualization.

Zabbix is Open Source, there is no licensing or pricing. As with any monitoring tool, there is a time cost which is required to learn how to use it well.

We evaluated Nagios. We preferred Zabbix for the easy to use GUI and because it is 100% Open Source.

In our opinion Zabbix is an amazing monitoring solution which allows for any service or device to be monitored. In most cases, integration is supported out-of-the-box. In some cases, additional scripting or minor development is required.

• Stability
• Flexibility
• Expandability

My favorite features are auto-discovery and LLD (low-level discovery) with Zabbix (and with some programming experience), you can monitor absolutely everything.

Also, it is worth mentioning the good quality of documentation and great community support.

Before we implemented Zabbix, we were blind.

I'd like it if they'd have implemented some sort of SNMP auto-discovery.

Almost seven years (from version 1.8.2).

There were some issues, then I made an upgrade from version 1.8 to 2.4.
I had to migrate existing MySQL DB (that is sitting under the hood) from one engine to another.

Yes. But again, it was an upgrade issue.

From the very beginning, I used distributed monitoring that was based on the Zabbix nodes conception, but they got rid of the nodes since version 3.0.0.

So, I had to change Zabbix Nodes with Zabbix Proxies. Finally, I have found out that the Proxies have better performance, stable matching, and are easier to configure than the Nodes.

I know they have one but I never had a chance to use it.

Before Zabbix, It was another Open Source solution: Nagios. Actually, I set them both up simultaneously.

So, I had a chance to compare them side-by-side. Finally, I chose Zabbix.

Setup is the very first step. This step you have to perform just once. The process is easy and straightforward, but the product itself is not easy to use.

I would suggest reading documentation before the installation. It has a steep learning curve.

The monitoring of IT infrastructure is not a piece of cake. Don't think you can install it with a couple of clicks and be done.

To implement have a good implementation, you have to read the documentation thoroughly.

Like any other Open Source product, you can spend some money on support, but the product itself is free of charge.

No, I did not evaluate other options before choosing this product.

The most valuable features are the monitoring and the ease with which we can set it up at customer sites with our custom Zabbix proxy and tools. It is very agile and it is easy to do custom setups.

The dashboard and the graph section could be a little bit more professional.

We have been using Zabbix for about five years.

There were no issues with stability, but we needed to adjust some of the standard values in the configuration. However, that was to be expected.

I haven't scaled yet, but we plan to do this with two front-ends, two Zabbix cores, and HA MySQL.

We haven't used technical support yet. I have attended a course with one of the employees at Zabbix, and he was very good.

We did not use a solution previous to this one.

The initial setup and the subsequent upgrade were both very easy.

There are no licenses.

Just go for it. The possibilities are endless and very large.

Scalability, everything can be monitored.

Reporting is weak, if you want something better you must write your own SQL scripts/

3 years.

Sometimes.

Yes, web-page Zabbix server, database can be separate machine.

Never used the technical support.

Yes, previously used Cacti or Nagios but Zabbix has node communication.

Straightforward, if you understand basic things about databases or web services, it's easy.

All data is stored in the database. If you have more than 200 hosts you need a fast disk or good tuning of the OS/database.

We value the auto-host discovery, template import, bulk import/export features. Newer versions also add nice features, such as multi-IP per host.

We operate an HPC cluster. On several occasions, the datacenter(s) counted above 1000 hosts. An easily scalable solution is most valued against other solutions which are simpler to operate and have a smoother learning curve, such as Nagios.

The design of Zabbix allows the user to change metrics and check on the server side, instead of changing them on the client side, via a configuration file.

I use an older version of the product, so I cannot answer this question.

We have been using the solution for seven years.

The underlying database needs proper tuning and maintenance to avoid table fragmentation.

We had some scalability issues with a large number of nodes. It was as if the underlying relational database is on the same machine and has fragmented tables. The server CPU could ramp up to 100% and the metrics are not refreshed properly.

We switched in order to get the benefit of the ability to redefine metrics server-side, nested templates, and the really powerful graphs available at the time.

The initial setup was really straightforward. However, as soon as you reach 100 monitored clients, the default MySQL configuration doesn't scale up. I'm sure that a newer Zabbix version relies on better backend solutions for data storage.

It's free software released under the GNU/GPL license.

We evaluated Nagios.

It is unnecessary if you have below 100 hosts. Otherwise, it's a great tool, with a nice web interface.

Dashboard and the customization of the items and triggers are the most valuable features.

With just one look at the dashboard every morning, we can anticipate problems.

It should be easy to modify the front end.

I have used this solution for five years (started out with v1.8).

There were no stability issues.

There were no scalability issues.

Previously, we were using Nagios. The front end was poor so we switched over to Zabbix.

The product is an open source and free solution.

It's a complete solution. There is a learning curve but it is worth it.

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.

It has various features, I like its versatility the most.

It not only provides the preconfigured item monitoring feature, but it is also easy to configure custom items.

The template is another valuable feature, because hosts can be easily added.

My organization can get a proper alarm when some issues occur on a system.

Even though it’s such a powerful monitoring system, it would be more helpful if it had a flexible UI.

I have used this solution for more than three years.

There were no stability issues experienced, it’s so stable.

There were no scalability issues.

I’ve never used technical support because it is free.

I did the setup by referring to its documentation and that was enough.

It’s free of cost.

I checked Nagios, but I didn’t seriously evaluate it.

The documentation has all the information you need.

Zabbix is fully open-source - no paid features/versions, so you get everything for free. Great, totally free product:

• It is very customizable and flexible - you can monitor almost everything.
• It has many great options - like auto discovery/registration, many types of alerting and templates provided by the vendor.
• It is easy to implement, easy to use for technical people.
• It is very stable, flexible and scalable.
• It has many great features ready to use right after installation.
• It is a little hard to understand for the non-technical user.

Zabbix allows us to monitor critical parts of our systems, track performance and utilization, and prevent outages.

It allows us to monitor specific parts of the system as well as control how the whole environment is doing.

With the great alerting system we always know which component might fail and can prevent it.

Adding new hosts/items is easy and quick and the great function for mass updating many components at once is very helpful as well.

Zabbix is a great tool and fairly easy for a technical person but it could be more friendly for non-technical staff.

We have been using the solution for two years.

We did not encounter any issues with stability. Zabbix is very stable. I can't remember a Zabbix server ever failing.

We did not encounter any issues with scalability.

I've never contacted Zabbix technical support. I had no need to. The Zabbix forum was enough for my issues.

I switched from Nagios to Zabbix. For me Zabbix is more intuitive, flexible, offering more options out-of-the-box.

I didn't have troubles implementing it. The official documentation is more than enough.

Zabbix is free - no hidden costs, no paid features. Just download, install and enjoy.

I had the option to stay with Nagios or switch to Zabbix. I switched.

Make a plan for components you want to monitor, how these components are related, what groups and templates you want to create.

Also at the beginning don't be afraid to use templates provided by Zabbix - it will help you start. After that you can slowly tweak them or add new ones.

Make the database backup - that should be obvious.

Zabbix is very flexible and scalable.

The UI is hard to get used to.

2 years

• Automated network discover (ICs, servers, switches, routers, etc)
• Automated item/metric discovery (partitions, network interfaces, users, databases, virtualhosts, etc)
• Flexibility to 'learn' things (is trivial to extend ZABBIX features)
• All things (historical data, configuration, etc) are in database
• Automated inventory hosts (hardware and software)
• Web monitoring (a robot to check websites)

ZABBIX is a 'all-in-on' monitoring solution. We don't need any other monitoring tool since we use ZABBIX.

• ZABBIX is a 'all-in-on' monitoring solution
• ZABBIX is 'true open source'
• ZABBIX is 'Commercial/Professional' supported
• ZABBIX has a 'centralized' approach. All things are done using the ZABBIX GUI

Open Source: All the sources for all the products are Open Source, so you can use a complete product from the start. There are no "premium" features with additional cost.

It gives you visibility over your infrastructure, so you are able to know the health of your services and it's dependencies every moment (and even to react automatically to problems). For example, in one organization I worked for, before Zabbix the problems were normally reported by the clients using the call center, so the Operations team was always working against the clock and with high levels of stress; after a successful implementation of Zabbix, putting the right monitors in place and a period of stabilization, the Operations team had the information to prevent the problems before the clients were affected. This resulted in a Operations team with lower levels of stress, more time to work on important projects and client satisfaction by lowering the number of problems visible by the client.

The low discovery functionality is still very young so this feature has a lot of room for improvement. The graphics generated by the system can be improved and also the web interface. At this point in time it's possible to archive a good level of security by using external tools, but it would be nice if this level of security could be archived out of the box.

I've been using the solution since version 1.4 which was around 2008, so I've been using the product for six years now.

Having the right knowledge, the installation and implementation of Zabbix it's very simple, even the principal Linux distributions already have a Zabbix version in their repositories. A successful implementations requires the knowledge of what it's necessary to monitor and the way to do it, but this is true for all monitoring products.

No, the software is very stable as well as the the components it depends on (in my case Linux, Apache, MySQL).

No, Zabbix is very scalable and well programmed, also gives you elements to identify when the performance could be a problem and can be configured in a very granulated way. Also, the principal components can be separated and gives you options to distribute the monitoring (archiving horizontal scaling).

I don't have first hand experience with the Zabbix SIA support, but the support the community provides it's great.

Based on the information I can see in the Zabbix forums and social networks I would say Zabbix SIA have engineers with an excellent technical level.

Yes, the principal reasons to switch to Zabbix were: Flexibility (Zabbix allowed the monitoring of something the other product does not), cost (no license costs, it was possible to monitor something with no extra costs, the hardware necessary for Zabbix was much lower) and in the tests Zabbix outperformed the other products evaluated.

The first time I installed the product (back in 2008) my initial impression was the software was complex to install, basically because at that time the repositories of my Linux distribution had an old version of the software and I wanted the most recent so I installed the software by compiling the sources; but once you understand, document and become familiar with the process it's pretty easy. Also, at the beginning understand the philosophy behind Zabbix was a little complicated but equally once you have the knowledge it all become easy and natural. Another aspect you can consider complex in Zabbix it's the lack of detail in some templates, so if you only use the out of the box templates (without changes) you ended up with a basic monitoring, most of the time you will need to extend the template to adjust it to your specific needs and obviously this will require knowledge of several aspects (this can be seen as an advantage or a disadvantage).

I've been responsible for about 4 Zabbix implementations and always was in-house job.

In this case, again, I don't have numbers. In the last implementation, the original cost was only the cost of the hardware plus the salary of the sysadmin responsible of the system, the day to day cost it's only the salary of the sysadmin. No fees for licenses and no fees for support at this time.

Yes. Nagios: This product it's the de-facto for open source network monitoring. System Center Operations Manager: The monitoring solution of Microsoft.

My advice is that its good to have a clear understanding of the goals you are looking to fulfill with the monitoring system, the objectives must be clear, also the environment in which the system will be implemented and the capacities (hardware, people, time, etc). There are a lot of aspects to take into consideration when choosing and implementing a monitoring system so invest as much time as possible in planning carefully. Zabbix is a great product, with great flexibility and I'm sure can be adequate to most of the situations, but maybe it's not the best choice in some scenarios, so plan carefully before choosing and implementing any product. For example, I would not suggest an in-house Zabbix implementation to a company without technical staff.