Zabbix Reviews

Dashboard and the customization of the items and triggers are the most valuable features.

With just one look at the dashboard every morning, we can anticipate problems.

It should be easy to modify the front end.

I have used this solution for five years (started out with v1.8).

There were no stability issues.

There were no scalability issues.

Previously, we were using Nagios. The front end was poor so we switched over to Zabbix.

The product is an open source and free solution.

It's a complete solution. There is a learning curve but it is worth it.

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

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. 

• Monitoring servers
• Health and communication links availability

By using the solution, we moved from a reactionary approach to a proactive evaluation of our equipment/systems.

Look and feel.

Six years.

Not in the version we’re currently using.

No.

We only use the free version without support.

Yes, we used to use another solution. We migrate to Zabbix after evaluating when it was implemented as a part of a web-based software solution that was acquired by the company in which I was working at that time.

The installation process was simple.

Nothing, because we’re using the free version, which covers all our current needs.

No.

You’ll be pleasantly surprised if you give the product a chance.

• Multi-level infrastructure maps. You can set up highly customizable maps of your infrastructure, including each component status, maps which can contain submaps, and if something’s wrong at the submap level - the submap will be shown with problems.
• Agent and agentless monitoring. Installing an agent is the easiest way, but SSH, SNMP, Impi, custom scripting and other protocols are supported.
• Templates. There are a broad set of templates that define monitoring items for common OS and applications, you can build your own or use one developed by the community.
• An API for you to create, modify, and delete most things programmatically, including items, triggers, charts, etc.

As we know how are systems are supposed to work, Zabbix has given us the flexibility of building our checks without relying on special plugins. If some monitoring item is not provided already, building your own is very easy, and any scripting language will do. We’re able to pinpoint with accuracy where issues lie, and respond to them in a cost effective way, due to the nature of it being open source, with fairly decent documentation and optional commercial support.

The Java gateway for monitoring Java applications didn’t work for us. Our JMX Service URL’s are somewhat complex, but we were able to write our own JMX checks.

Three years.

When your checks grow to a certain volume, you need to adjust some settings on the server related to cache sizes, preforked workers, and so on. This is expected as with any service that grows beyond its default settings, there’s documentation about it.

The system is as scalable as your database is. We applied partitioning on the biggest tables to keep the performant at 14 new values per second. You can setup a distributed architecture consisting of an N number of proxies capturing data and reporting to N master servers.

Fortunately, we’ve never needed it, because we have very talented engineers in our team and there’s plenty of documentation available online. There are also user forums which are helpful most of the time.

A fork of Nagios called Icinga, it’s pretty good, but something like the Zabbix Maps feature was a must have for us. We needed something very schematic and flexible to show the overall status of our systems.

It wasn’t complex, but we have very skilled engineers.

The quickest way to go is to have a turnkey virtual instance tailored to your needs by Zabbix, or use one of the freely available ones.

The product is open source with optional commercial support, which is recommended to reduce the learning curve, avoid pitfalls, and keep the project going.

SolarWinds. Nice product, but our particular project was more in line with the Linux, PostgreSQL, and the Open Source philosophy.

If you’re into the Open Source and freedom principles, don’t mind getting your hands dirty, and have the technical skills, Zabbix is a good choice. Commercial support is available if you don’t want to go at it alone, lack sufficient technical skills, and you need help to keep the project going.

Scalability, everything can be monitored.

Reporting is weak, if you want something better you must write your own SQL scripts/

3 years.

Sometimes.

Yes, web-page Zabbix server, database can be separate machine.

Never used the technical support.

Yes, previously used Cacti or Nagios but Zabbix has node communication.

Straightforward, if you understand basic things about databases or web services, it's easy.

All data is stored in the database. If you have more than 200 hosts you need a fast disk or good tuning of the OS/database.

SNMP monitoring, source discovery, and alert triggering are most valuable.

It is a very easy product. Its dashboards are good and interactive. There is very good information.

We are able to use the Zabbix API for integration. We could integrate System Center Operations Manager and Zabbix with APIs to create a new product or alerting system. 

The System Center Operations Manager can be improved. 

Cloud monitoring can be a bit easier, and the Zabbix dashboard can be developed a little bit more.

There could be integration with Ansible Tower or AWX CLI.

I have been using this solution for five years.

It is stable.

It is very easy to scale. Many customers use Zabbix. We have one Zabbix center with 10 customers. We have a Zabbix proxy and centralized monitoring.

We have never used their technical support.

Its deployment is easy. Virtual appliances are very easy, and Zabbix agents are supported across different platforms, such as Linux and Windows. I would rate it five out of five in terms of the ease of the setup.

It is a good product. It is easy to integrate and use. We are happy with it.

I would rate it a nine out of 10.

We use Zabbix for monitoring server network equipment. The solution is deployed on-premises.

We have 10 technical engineers using the solution.

Zabbix allows us to monitor a lot of hardware equipment without any additional cost.

Most of the out-of-the-box features are valuable.

It would be helpful if they translated the documentation to Cyrillic languages.

We have been using this solution for five months.

From time to time, there are agents failing, but it's not often. I think it's stable.

The solution is being used every day because it's a monitoring system.

For our company, it is not scalable.

Support is given through tickets, but I'm not directly in contact with Zabbix support.

I have previously used SolarWinds.

Setup was straightforward. Initial deployment took two or three months.

Implementation was completed by our engineers.

We pay the subscription for support by year.

I would rate this solution 8 out of 10.

I can recommend Zabbix as a monitoring system.