Zabbix Reviews

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. 

Zabbix is used for monitoring infrastructure, including networks and servers. It is used for monitoring the performance of each device. It can also be used for application monitoring, but the integration is not easy.

Zabbix is an excellent performance monitoring tool. It's an open-source tool, and it's free to use. You don't need to pay anything, and it uses little resources. You can use Zabbix if you have a small infrastructure and not a critical one.

The integration of the product is not so easy, especially when it comes to the application database. Finding customized agents for each product needs some deep understanding. They also don't have a license for the product, but you can purchase a support contract they provide.

Unlike NETSCOUT, Zabbix lacks the capability to work purely on packets, drill down on root causes and monitor any infrastructure regardless of the vendor.

We have been using Zabbix for one year.

The product is stable, and it is a very good product.

Approximately 10 to 15 people are using the solution in our company.

Zabbix is an open-source tool, and it's free to use.

Zabbix is a really good tool because it is an open-source tool.

In the future, we might consider using products like NETSCOUT, capable of root cause analysis, which works at the pocket level and can give us some insights into our overall infrastructure.

Overall, I rate Zabbix an eight out of ten.

Our primary use case is server and network monitoring.

The features I found most valuable are the user interface and a wide range of network devices that are easy to configure.

I would like for this solution to be more cloud-friendly.

I have been using this solution for about one year.

I would rate the stability of this solution a nine, on a scale from one to 10, with one being the worst and 10 being the best.

Previously, we used Splunk and we switched because the solution's pricing was too high.

I would rate the initial setup process a seven, on a scale from one to 10, with one being the worst and 10 being the best. Our model of deployment is on-premises.

This solution was used by 200 people in our company.

I would rate this solution an eight, on a scale from one to 10, with one being the worst and 10 being the best.

We use Zabbix to monitor the configuration and usage of devices on the network, including switches and printers. 

Zabbix alerts us about problems on the system, including damage to the hardware or network connectivity issues.

I'm supervising all the IT departments, and Zabbix seems quite good for them. It provides graphics and information in real time. We get alerts about crashes on the system, enabling us to quickly repair issues. We can easily find devices with problems.

Zabbix is powerful, but it is difficult to understand initially. There are many things that can be improved, but we might not be using Zabbix to its fullest extent. The software has more features than we need.

For example, Zabbix can be used for a company monitoring solutions by many vendors. We have only one site and one company, so we can't improve all the possibilities of the software.

Zabbix could add some more cybersecurity features. It isn't the same thing because network monitoring isn't the same as security. Still, it could include something like a VPN or firewall with the solution. It's a free software tool traditionally used for monitoring. 

I have been using Zabbix for around one year.

Zabbix is highly stable.

I rate six out of 10 for scalability.

We don't use technical support. We rely on the documentation. 

We previously used Centreon, another open-source solution, about four years ago. I wasn't used to this kind of software, but now I can understand them a little bit better.

I rate Zabbix five out of 10 for ease of setup. It takes about two weeks to deploy. We have many people working from home, which creates some difficulties. Sometimes, people left materials at home when they work at the office, and we didn't have the time to install all the components. That's why it took time.

We saved time one equipment intervention, preventing service outages. We had the information about network blackouts before they happened, so we could save our company by changing equipment before we experienced downtime. 

Zabbix is an open-source solution, and there aren't any additional costs.

I rate Zabbix eight out of 10. It's a good solution for everyone's needs. Maybe same users that we have, few users for the moment because we don't have a very big important network. I think that Centreon is better, but maybe easier than the subjects to use. This is maybe the best solution for small entities.

We primarily use the solution for monitoring issues and availability.

This product is very easy to deploy. It is easy to deploy as a Docker if you do not want to do a full deployment. 

The initial setup, while not simple, is easier than other products.

It offers native support of VMware ESXi integration.

The solution is stable.

It's free; it's open-source. 

The documentation has been very useful. The community is quite helpful as well. 

The networking monitor is not too easy to work with. It's like switch monitoring. It's okay, yet not perfect. It's something they could improve on. I'm still using SmokePing since the network monitoring isn't so great.

The initial setup isn't exactly easy.

I've been using the solution for one year. 

I've found the product to be quite stable and reliable. There aren't bugs or glitches. I do not have issues with it crashing or freezing. 

I cannot speak to the scalability of the product. My scale is quite small. I've never reached the limit o the server. 

I'm the only one who uses the product right now. I only use it in my personal lab and therefore have no plans to expand usage right now. 

I've never dealt with technical support. I cannot say how helpful or responsive they are. 

A long time ago, I used Zenoss. Zenoss basically focused more on larger enterprises. The community version of Zenoss was less well-maintained. Zabbix has a better community. That was a major reason for switching. 

The implementation process was okay. No monitoring tool is easy, I would say. It's not extremely easy, and yet, it's not extremely complex like some of the other tools. There's a moderate level of complexity during deployment. The entire process takes a couple of hours.

For my level of usage, I only need one person, and that is me, to handle any maintenance tasks. 

I handled the implementation personally. I did not need the help of or use integrators or consultants.

In terms of ROI, it's been providing faster troubleshooting when there are issues. It provides a good dashboard to show global health. 

This is an open-source product, which makes it free to use. 

I'm a customer and end-user. 

We're currently using the latest update of the product. 

I'd rate the solution eight out of ten. 

We deploy it for our customers.

The main use case is monitoring of the workplace services. That means lot of VDI systems, little machines, and all that stuff around office routers, switches, and even printers for example.

The Zabbix agent is one of the highlights. It's easy to deploy and self-registering into the system. This is very helpful. Using the template and the discovery, it's very easy to find examples from the community and make some changes if you need to, and deploy it and roll out. While the discovery is very easy, all the important things when getting connected is pretty straightforward.

The initial setup is very easy.

There is less computing power needed for scaling.

The solution is stable. 

It is open-source.

One of the real benefits is the API. You can do anything with an API; it makes life much easier. If you want to get reports or if you want to document something or you want to add something, you can use the API for that. That's really, really helpful.

The service module started with version six. There is room for improvement, due to the fact that this first step looks nice, yet it can be improved here for a better combination with the services and the dashboard. 

The event correlation could be better. From day one, we're using the API to create tickets for our operations, however, the correlation is not good, not there. A lot of the time, in that case, we are opening a few tickets for one problem, and then the correlation functionality is very, very limited.

The reporting is lacking. It is there, however, it's not a real reporting from my perspective. Reporting in Zabbix means you create a dashboard and then you can schedule that and you get it as a PDF. It's probably not the reporting most operations need especially if you need more data for importing Excel or whatever. Reporting is even, in a lot of ways, missing. In the other end, we are using the API to do that now. That said, the issue there is you need the developer to do that if you decide to go that route.

I have one year of experience with this solution.

The stability is good. I would rate it five out of five since we have no issues. It's been running well since the first day. We did two release updates in the meantime, however, there was no reason to restart something. The performance is very good. 

We have around 50 people using the solution. It is mostly the operation teams from different departments.

I was wondering if an open-source solution would scale well, since we have experience more with a lot of other enterprise tools, including Broadcom and HP. There are others which need much more resources to monitor the same devices, I would say. However, if you go to an enterprise solution like Broadcom or HP or ScienceLogic or BMC, you need much more infrastructure for monitoring than you do if you use Zabbix. In this sense, I can say it scales well. 

I'd rate the scalability five out of five. 

We haven't used the support from Zabbix so far. At the moment, all we are doing is using the manuals to troubleshoot. The documentation is good. Otherwise, we are using the community forum if we have any questions especially for creating templates or something like that. The community forum is great.

The initial setup is very straightforward and simple. It's easy, not overly difficult. 

We started with just one single device, one single server, since we did not have too many devices. We have, I'd say, around about 2000. However, we found it enough to monitor them all with one device. We have one device for a UI, for the application and for database as well and it's just one single server. We started with that and figured out, from the performance, it was more than enough.

The deployment, just for the application, took less than a day. It was quick. There was not too much to do. 

Our team managed the deployment. We did not need outside assistance. 

The solution is an open-source product. We are using that version and have yet to purchase a license, which we may do further down the line - maybe a year for now.

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

The good thing is that it is easy to test. This is one of my favorite benefits and why I like open-source software. You can test it very well without signing contracts with enterprise vendors, for example. New users should put it on their laptop and try it out. It doesn't need much resources and you can discover your home network or your lab if you have something. 

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

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

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

The initial setup is easy.

It's a stable solution.

We find the product scalable. 

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.