Zabbix Reviews

I'm using it to have a global map overview of all my machines. We also use it in simple scenarios to check that our applications are up. We haven't really created that many dashboards at this time, but our next mission is to create good dashboards to efficiently track the VM performance.

There is a problems page that shows us every warning or problem that occurs on our VMs globally. The map screen is also really useful because this is something that was missing. I don't know every other tool in the market. So, I don't know if this is a good point of only Zabbix, or other tools are also doing it, but from my point of view, this is the most useful page that I use, along with the problems page that efficiently lists the problem, recovery time, ending hours, starting hours, and so on.

In terms of user-friendliness, large maps could be more interactive. We should be able to click on some areas and move some objects. It would make it simpler to see things while analyzing some dedicated parameters.

It has been six months.

It is stable.

It is scalable. We have 15 to 20 users of this solution. It is used by the IT department. So, the operations teams, which is my team, and the system admin team, which is in charge of the infrastructure and the network, are its users.

I have never contacted them.

We used Centreon previously.

I was not a part of the deployment project, but I didn't hear that the deployment was complicated. The tool is very detailed, and maybe the configuration needed afterward to do the setup everywhere might be heavy.

From a user's perspective, I would rate it a nine 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 mainly use it for server monitoring, like checking how much storage is available. For network devices, we use PRTG.

The most valuable feature is that it provides network segregation for server monitoring. The server selection is easy to use in Zabbix in comparison to PRTG. We want to move the Zabbix servers into PRTG. We use PRTG for network devices and Zabbix for server segregation for the initial days.

Zabbix is not easy to configure, and upgrading is also an issue. But for PRTG devices, we can configure it on our own within half an hour. Besides, Zabbix is not easy to understand. The interface we need to check and what steps are to be taken to do so needs clarification. The new joiners need help learning to utilize it as they need to check the steps individually. Also, there were graphs in the earlier version, but the present version has blocks and no graphs.

I have been using this solution for four to five years.

There are some glitches with the stability. Currently, 30 servers are using it.

It is easy to scale. It will have a few comments, and after running that, it will install. I would give it a seven out of ten.

The initial setup of Zabbix is complex as it is installed on Linux machines. Besides, every package has to be installed individually. Even if one package is missing, it will not be installed. So everything needs to be checked. It's too much of a headache. The solution got deployed on the cloud.

My company makes payments to Zabbix regularly, but I am not sure.

I will rate this solution a seven out of ten.

I use Zabbix for monitoring. For example, monitoring networks and applications.

The solution has been proactive in altering while monitoring which has been helpful.

The most valuable features of Zabbix are flexibility and a single interface for different types of monitoring.

Zabbix could improve when it comes to large-scale use cases. Additionally, the inventory could be better when connecting to other solutions, such as ServiceNow. There show to be better integration with other platforms and storage.

In the solution's next release, customizing scripts could be easier and API interactions could be better. If they would allow larger data metrics on one chart would be helpful.

I have been using Zabbix for approximately four years.

The stability of Zabbix has been good.

We have approximately 300 network devices being monitored, including data center monitoring. Additionally, we monitor servers by different performance metrics and services.

Old versions of the solution do not scale well. We only had one master server and we had to switch off and turn on other features to allow scalability. It was not easy.

I have not used any support for the solution.

The initial setup of Zabbix is of a medium level of difficulty. The documentation is beneficial.

For a middle-sized integration of the solution of approximately 100 hosts, it can take one to two months to do all the necessary layers.

This solution is open-source and free to use.

The solution has quick integration, templating, mapping, and monitoring.

I rate Zabbix a seven 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.

We primarily use it for monitoring, but also for some other things.

In terms of customization and integration, we have more flexibility. We can automate configurations, define deletion rules, and customize based on your needs. The client interface allows for further configuration, making it quite comprehensive.

Architecturally, we can even extend to the cloud using Suncoast servers and proxy servers to communicate with WorkRock or the supervisor. The compatible database list makes configuration straightforward.

User-friendliness is another strong point. We have a customizable dashboard. We can define metrics directly in the web portal, avoiding editing configuration files. This provides several advantages, especially when managing multiple collections.

There are areas of improvement. The database grows really fast. So, when you install Zabbix, you have to deal with some issues, like the database. We become pretty big very fast. 

This leads to optimization challenges, requiring manual deletion of network components like SNMP. We should work with SNMP. It's not as simple as configuring the host incident.

Configuration can also be difficult. The use of a workflow in the configuration of items or triggers makes it difficult to use an item in a mature way. It's hard to set up a dynamic workflow. While workflows exist, setting them up for specific data sources like network items can be a hurdle. You may need to find alternative methods, which isn't ideal.

For some customers, there are some personal customization challenges. But, for me, it's okay.

I have been using this solution for a year. We use version 6.0, which is the next recommended version. We don't do long-term tests, so it is a middle version.

The latest long-term support version we're using is 6.1.0.

I would rate the stability a seven out of ten. 

There are around less than 20 end users in the company. These include admins, managers, and engineers. 

I would rate the scalability an eight out of ten. 

I work with the public community like a public forum. So, when I have a request, I use the public community forums. We usually find solutions within a day or two, depending on availability.

Neutral

There are many options available. Today, you can use alternatives that provide better-detailed information. For instance, we have alerts concerning specific issues. I'm using Azure as part of this organizational setup. 

In Zabbix, for metrics, the latest release is better, and we can also find some metrics. Essentially, we don't incur any cost of the same magnitude. In Zabbix, images allow us to view the bot system today for Windows, Linux, infrastructure, and networking processes.

The installation itself took about one to two hours. The lack of clear step-by-step procedures. There are procedures, but they're not very detailed or user-friendly.

There is a team of admins to supervise the product. 

Zabbix itself is free, but professional support is paid. They have different pricing tiers based on the category and enterprise level. You can find the detailed pricing policy on their website.

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

We are using the solution for network monitoring for all of our appliances and devices as well as servers and switches. 

The solution offers a lot of templates, so you can find a template easily that will suit your needs.

There are a lot of graphs that are really useful. 

Once it's installed and working, it's very nice for monitoring.

The solution allows for good integration with other products.

It is stable. 

There is a bit of a learning curve during installation.

Support could be better. 

It's quite stable. There are no bugs or glitches, and it doesn't crash or freeze. It is reliable. However, if there are problems inside your host operating system, it may have an effect on the stability of Zabbix. 

I don't really have experience with big networks. I can't speak to the overall scalability. 

Support needs improvement. If you pay for it, it's fine. However, when you do not pay for support, you'll need to find answers to your questions by yourself. 

I do not have experience with other products. 

The solution is pretty straightforward to set up. It's not complex at all. I'd rate the ease of setup eight out of ten overall. There may be a bit of a learning curve, however, once you understand the solution, the setup goes smoothly. When you are new, if you make a mistake, you have to redo something. It's better to set up a virtual machine so you can take a snapshot.

You do have to pay for support. 

I'd rate the product nine out of ten. 

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.