Zabbix Reviews

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.