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 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 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 are using Zabbix in my workplace to monitor the infrastructure.

We are able to monitor our virtual infrastructure, virtual machines, windows servers, databases, and the network using a simple network management protocol. We are able to pull almost all the metrics that we want, receive notifications, and have them integrate with telegrams for certain devices that are critical, such as UPSs.

Zabbix does not draw automatic mapping of the network, this is something they should add in the future. There is a lot of effort that is involved in tailoring some of the settings which could be made easier. 

I have been using Zabbix for approximately four years.

Zabbix is scalable because depending on the size of your infrastructure you can have distributed proxies servers across your network that will feed to the main server for the metric. It is similar to branches, where you can have one product for each branch and then the central server speaking in your central location, it works perfectly.

Our entire IT department is using Zabbix, which is 15 people, but we have approximately 600 devices being monitored.

I have never had an issue that I needed to contact support. However, everything I have needed was able to be found online from the community or the Zabbix site manuals. Zabbix does offer support based on a subscription.

I was using Centurion previously but I decided to switch to Zaddix because of costs. I was using the community edition of Centurion and it was very limited but with Zabbix, you can have an enterprise-class monitoring solution for free. I did research quickly and then I phoned Zaddix to see if they could solve all my problems without having to pay anything. This is when they confirmed I could and then I switched.

The initial setup was easy. It took approximately three hours to get the server up and running.

By using Zabbix you minimize the cost of operation because you recieve an enterprise-class monitoring solution for free.

The solution is free to use but they offer support as a paid service. If you can go read the manuals and do the fine-tuning based on your needs, you do not need to pay anything and you will have a full solution.

I have evaluated PRTG and SolarWinds.

You do not need to spend a lot of money on solutions that have similar functionality, such as PRTG or Solar Winds. With Zabbix, you receive a free enterprise-class monitoring solution for free, as long as you know how to use it.

I would recommend this solution to others.

I rate Zabbix a nine out of ten.

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.