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.

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 use Zabbix to monitor the threats in the IT infrastructure. 

Zabbix helps to save time. 

The solution needs to add remote features. 

I have been using the solution since 2017. 

I rate Zabbix's stability an eight out of ten. 

My company has 20 users for the product, but around 60 people enjoy the benefits of it. I rate the tool's scalability a nine out of ten. 

I have yet to reach out to the support. 

Zabbix's installation is easy. It is also easy for customization. 

The tool's licensing costs are yearly. 

I rate the solution an eight out of ten. 

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.

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 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.

As a network services provider we use Zabbix to monitor network infrastructure and customer services. I have also set instances for a number of government institutions to monitor their entire ICT Infrastructure. I will focus on the largest instances, the service provider use cases.

I used Zabbix to monitor network devices, servers, databases, virtual machines, services and applications. For the network services provider, I run an instance for our internal infrastructure and another instance for monitoring our customer services so they can have access to monitor the state and status of their services, SLA, view utilization graphs on demand or in real time and produce needed reports and also receive alerts when problems happen

We could easily monitor anything on our infrastructure and customer services using Zabbix as a consolidated solution for all the network infrastructure and customer services monitoring needs , as Zabbix is highly flexible and customizable to fit the specific needs of organizations.

Zabbix has greatly improved  operations and maintenance by helping management and technical teams be more proactive. They can easily spot problems or undesired states on the infrastructure or customer services

With the Zabbix out-of-box multitenancy support,  customers can have restricted access to their service utilizations and other operational data in real time or on demand. The feedback from customers shows they are very happy and they appreciate how easy it is to learn using it.

Time to work on issues is greatly reduced, as Zabbix provides powerful alerts and details into what is happening in our network. Issues that could take weeks to resolve can now easily be spotted in a few minutes as all essential metrics for all devices are monitored in real time.

Zabbix fits well with the multi-vendor environment and it has a lot of out-of-box templates that can be customized to fit our needs.

We can easily provide infrastructure status reports with Zabbix. We can produce reports even for old devices that were not properly and consistently monitored since they were installed.

Zabbix is highly customizable and flexible, which makes it easy to have all our monitoring needs accommodated. Many elements like auto-discovery, dashboards, templates, graphs, maps, metrics, SLA's can easily be customized to fit specific needs

Zabbix has a powerful API that support integration with third party software, automation and creating new applications. It can be easily integrated with other  tools as a data ingest, processing or visualization platform. The API allows for utilizing better software in specific areas that Zabbix may be lacking like Grafana which allows for more customizable dashboards.

Auto Discovery and Custom Actions are greatly helpful in doing mass discovery, the grouping of hosts, and templates association. The flexibility in setting discovery rules and actions is really helpful for complicated use cases.

Multi-tenancy support which a result of granular use roles, automatic actions, tags, and host grouping. User permissions can be limited to specific sections, services, applications, device groups, access level etc. This has proven to be very helpful for our customer's services monitoring instance.

Out-of-box templates that are customizable, can be changed or modified to suit specific use cases. Additional items can be added to these templates and more filtering or pre-processing rules can be specified in these templates

It has an intuitive UI with beautiful graphs and customizable maps. Although more powerful solutions can be used, Zabbix caters for all our needs in that area as it provides the flexibility we need.

Zabbix provides regular updates and a clear and timed roadmap. Very helpful as our c company can see whether  expectations will be taken care in coming releases of the software.

Although Zabbix is great, the documentation is a bit lacking. The documentation gets a bit messy between versions and is not too detailed, the learning curve is steep and can be difficult for first-timers, especially when they run into issues.

Zabbix depends on other open-source projects, so it would be a good idea to add more information on fine-tuning a Zabbix instance especially the essential details when working with specific choices of OS, database, webserver etc. I had to do most of the things with limited resources in the fine-tuning of the database, OS, and other packages. Although not entirely a Zabbix issue it is a good idea to provide guidance on the basics.

Automatic maps. It would be great if Zabbix could create automatic topology maps using discovery protocols like LLDP or CDP.

Automatic Updates of host templates. It would save a lot of time if that could be done with new releases while keeping personal configurations intact.

Out of box high availability setting for all sections of Zabbix

I have been using Zabbix for four years

This is a very stable solution. It is a low maintenance solution and if finetuned and optimized properly can handle a heavy workload with minimum resources.

This product is highly scalable.  HA and redundancy can be set for database, proxy and front-end.

Zabbix experts provide great ideas on the open-source forums for the products. The Zabbix community, including the CEO and the technical experts, are friendly. Since they are doing great with the community, I am confident they are doing great with their optional Technical Support which we have not subscribed to.

Positive

I had used other solutions before but the licensing was too expensive for our company and still, other solutions were limited because we have a multi-vendor environment.

The setup is a bit complex but can be done with the right  skills. More important than the initial setup is optimization and finetuning which requires multiple skills.

We implemented it in-house. I primarily worked on the database, Zabbix server, Zabbix proxy, frontend and other server side stuff. I also prepared agent and SNMP configuration scripts for other Engineers to implement on network devices and servers.

I can confidently say that our ROI is 100%.

Zabbix is open-source so if one wishes to implement it in-house, they must have qualified professionals to set up and optimize databases, Linux/Unix OS, PHP, Apache, and depending on what is monitored, a full-stack network and systems administrator may be needed.

Zabbix provides support although we have not subscribed to the support. We implemented the instances on our own and we also operate and maintain them on our own.

We had to evaluate several options including SolarWinds NPM, PRTG, OpenNMS, Cacti, Nagios, and Zenoss Core. We used Huawei U2000, Cisco Prime and PRTG for some devices before we switched to Zabbix.

Overall, Zabbix is a great product. I have been using it for almost two years, and I am very happy with it.

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!