"The network guardian, excellent product."
We use Zabbix in our company for the control and monitoring of each of the Gigabit Ethernet interfaces of the transport network, based on …
Zabbix
Zabbix
Zabbix
Overview
What is Zabbix?
Zabbix is an open-source network performance monitoring software. It includes prebuilt official and community-developed templates for integrating with networks, applications, and endpoints, and can automate some monitoring processes.
Read moreRecent Reviews
Reviewer Pros & Cons
View all pros & cons
Armando Gomez Alarcon
Analista
EMCALI - Telecomunicaciones (Telecommunications, 5001-10,000 employees)
Video Reviews
Leaving a video review helps other professionals like you evaluate products. Be the first one in your network to record a review of Zabbix, and make your voice heard!
Pricing
View all pricingN/A
Unavailable
What is Zabbix?
Zabbix is an open-source network performance monitoring software. It includes prebuilt official and community-developed templates for integrating with networks, applications, and endpoints, and can automate some monitoring processes.
Entry-level set up fee?
- No setup fee
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting / Integration Services
Would you like us to let the vendor know that you want pricing?
16 people want pricing too
Alternatives Pricing
What is Splunk IT Essentials?
Splunk IT Essentials Work is an IT infrastructure monitoring standalone option from Splunk, providing server health insights, as well as cloud monitoring for hybrid infrastructures.
What is Instana?
Instana, an IBM company since the December 2020 acquisition, provides APM services for SOA, microservices, containerized applications and Kubernetes, and cloud native applications, as well as discovery and monitoring for IT assets.
Product Details
- About
- Tech Details
- FAQs
What is Zabbix?
Zabbix is an open-source network performance monitoring software. The core program is free, with paid support from the vendor. It provides out-of-the-box templates from Zabbix and community developers. Zabbix includes network health measurements, including memory utilization, packet loss rate, and predictive trends in bandwidth usage and downtimes. These measurements can be adjusted using custom thresholds for network health and security issue alerts.
Zabbix also offers automation capabilities, including automatic network detection, configuration management, and report generation. It also enables remote and scripted remediation efforts when an issue is detected. The open-source format of the software is designed to support customization by users and the community.
Zabbix Technical Details
| Operating Systems | Unspecified |
|---|---|
| Mobile Application | No |
Frequently Asked Questions
Zabbix is an open-source network performance monitoring software. It includes prebuilt official and community-developed templates for integrating with networks, applications, and endpoints, and can automate some monitoring processes.
Reviewers rate Support Rating highest, with a score of 5.7.
The most common users of Zabbix are from Enterprises (1,001+ employees).
Comparisons
View all alternativesCompare with
Reviews and Ratings
 (147)
Attribute Ratings
Reviews
(1-2 of 2)- Popular Filters
Companies can't remove reviews or game the system. Here's why
Score 9 out of 10
Vetted Review
Verified User
We use Zabbix to monitor network assets and customer links to generate reports and resolve potential problems in its infrastructure.
- Monitor connection availability.
- Monitor network assets.
- Generate reports on the performance of network assets.
- Generate reports on the performance of customer connections.
- Increase the number of configurable triggers.
- Clean the interface a little more.
- Leave the operation a little lighter.
- It improved our view of how customers' network connections worked.
- We can make proactive monitoring more efficient.
- Better customer feedback, with data collected from monitoring through Zabbix.
Zabbix was adopted in our framework due to the value, the hardware requirements, the knowledge we had available and the vast documentation on the internet.
50
They are Level 1, 2 and 3 network analysts and IT analysts.
2
Knowledge of programming, the operation of network devices and servers.
- Monitor servers
- Monitor Routers
- Generation of charts showing performance of network links.
- Até agora não foram percebidas.
No
Zabbix replace PRTG
- Price
- Product Features
- Product Usability
- Product Reputation
An important factor in deciding to deploy zabbix in our organization was the extensive documentation and community surrounding the tool, making it easier to use.
I do not think of changing anything in the way it would proceed from the way it was done earlier.
June 20, 2019
Best FOSS software for monitoring
Zabbix is primarily being used to monitor servers and services running on them, though it is starting to be used also to monitor network components as well. Secondarily, it is being used as a Synthetic User Monitor for web applications.
- Collecting hardware data - CPU, Memory, Network, and Disk Metrics are collected and reported on.
- Flexible design - It is very easy to build out even very large environments via the templating system. You can also start where you are - network monitoring, server monitoring, etc. and then build it out from there as time and resources permit.
- Provides a "plugin architecture" (via XML templates) to allow end users to extend it to monitor all kinds of equipment, software, or other metrics that are not already added into the software already.
- Very complete documentation. Almost every aspect of Zabbix has been documented and reported on.
- Cost - Zabbix is FOSS software and always free. Support is reasonably priced and readily available.
- Zabbix is very complex and the documentation, while complete, is not particularly well organized. In particular, I would like to see step by step instructions (similar to the synthetic user monitoring example) for installation and setup; more about what some of the numbers mean; etc.
- Zabbix system requirements are artificially high to cover every possibility, yet rarely are those resources used. Would like to see segmented resource requirements based on the size of monitoring to more efficiently size an environment.
- Zabbix has some nasty "gotya's" that are not really addressed in the documentation. For example, when first setting up an environment, there is nothing discussing the order of setup (host group, then users, then host, for example); but doing it in the wrong order will make it much more difficult to use later on. A tutorial (or series of tutorials) setting up the first several devices would go a long way here.
- Not so much a con as an UGLY that is common to most of this class of software - Zabbix requires a great deal of detailed understanding across several different IT disciplines. DBA knowledge for maintaining the database, System Administration for setting up and maintaining the server(s) and its software, Networking for setting up monitoring of the network, each software package you will have synthetic monitors of, etc. In most larger organizations, that means a lot of collaboration, but in smaller organizations, where it may only be a single person or team doing all the work, it means someone must be deeply knowledgeable about each aspect being monitored. It is no longer enough to just know the OS it is running on and leaving it to the user to know the software, or the network team to deal with the network issues.
- Zabbix allowed us to see where issues were with a new implementation of software that was having issues at one site but not the other. With the synthetic monitoring piece in play, we were able to isolate and quantify the issue and see who and what was actually having an issue (as compared to the typical user response of "slow").
- It has taken over 9 man-months to fully implement across a 1600 server global environment. Some of that issue was due to the poor design of the environment (mostly due to M&A processes that were never fully integrated), but part of it was due to no easy way to distribute the agents. Now, with the very recent release of 4.2, there is an MSI to allow for GPO deployments to windows machines, which would help tremendously for Windows-based environments. (Linux and Mac environments will still require extensive scripting or manual installations).
- Zabbix alerting allowed us to start alerting L2 application and server teams to be aware of disk space issues and resolve them before an outage occurs.
- SolarWinds Network Bandwidth Analyzer, SolarWinds Database Performance Analyzer, SolarWinds Log & Event Manager, SolarWinds N-central, SolarWinds Netflow Traffic Analyzer, SolarWinds Network Device Monitor, SolarWinds Network Performance Monitor, SolarWinds Remote Monitoring & Management, SolarWinds Server & Application Monitor, SolarWinds Virtualization Manager, SolarWinds VoIP and Network Quality Manager, Solarwinds Storage Resource Monitor, Solarwinds Web Performance Monitor, Nagios, Zenoss Cloud, New Relic, Datadog, WhatsUp Gold, Dynatrace, Dynatrace Synthetic Monitoring and PRTG Network Monitor
Most of the SolarWinds are separated out, whereas Zabbix includes templates and capabilities for all of them out of the box. Other solutions listed include most or all of them to varying degrees as well.
New Relic is more for Application Monitoring, but the New Relic Infrastructure is a direct competitor. Datadog and Zenoss Cloud are similar. In all cases, infrastructure monitoring is both stronger and cheaper using Zabbix. It is also available on-prem, whereas these other options are not. However, the application side is better for New Relic and Datadog. Have not used Zenoss Cloud to determine it's strength in Application monitoring.
For SolarWinds (all components), WhatsUpGold, and PRTG Network Monitor, Zabbix is an equal competitor. It is cheaper up front, with no recurring subscription or renewal costs (though there are support costs if you choose to purchase it). It can be more difficult, especially compared to WhatsUpGold, which is the easiest to use of all of them (and least flexible). Overall, it is a question of where your money is spent moreso than how much with any of these options.
Nagios is FOSS software as well, but much more difficult to get to a usable state. Once in place, it is probably equal to Zabbix for maintaining.
Finally, Dynatrace is by far the best solution, but it is at a significant price over and above the other options available. It was just too expensive for us to consider our needs.
New Relic is more for Application Monitoring, but the New Relic Infrastructure is a direct competitor. Datadog and Zenoss Cloud are similar. In all cases, infrastructure monitoring is both stronger and cheaper using Zabbix. It is also available on-prem, whereas these other options are not. However, the application side is better for New Relic and Datadog. Have not used Zenoss Cloud to determine it's strength in Application monitoring.
For SolarWinds (all components), WhatsUpGold, and PRTG Network Monitor, Zabbix is an equal competitor. It is cheaper up front, with no recurring subscription or renewal costs (though there are support costs if you choose to purchase it). It can be more difficult, especially compared to WhatsUpGold, which is the easiest to use of all of them (and least flexible). Overall, it is a question of where your money is spent moreso than how much with any of these options.
Nagios is FOSS software as well, but much more difficult to get to a usable state. Once in place, it is probably equal to Zabbix for maintaining.
Finally, Dynatrace is by far the best solution, but it is at a significant price over and above the other options available. It was just too expensive for us to consider our needs.
30
We currently have 30 logins in the application but it is difficult to quantify the number who use it. It is a growing product and it has been expanding in use for the last 9 months. Currently, Infrastructure teams use it for server monitoring, and some application teams are starting to use it for application monitoring and synthetic user monitoring. We are trying to tie in Network teams as well to be able to start correlating server and network outages to get a better picture of the root cause. Ultimately, besides using it for these purposes, management is looking to use it to provide reporting on a variety of things, from server utilization to cost of an outage at various levels, to whatever.
1
I am currently the only in-house person supporting Zabbix and that is only part-time. That is part of why it is taking 9 months to roll out basic monitoring services. In reality, it would help to have 2 or 3 people who know the Zabbix application, at least 1 DBA (part time is fine), and someone who knows each application and/or networking members. This would spread out the implementation, especially with regard to agents and SNMP trap collection, while at the same time allowing people who know the applications best to be able to setup monitoring in a sane and useful way for them.
That said, once implemented, it only takes 1 person who is knowledgeable in Linux to maintain the application, and a DBA to maintain the database(s) (if it isn't the same person). This is independent of scale, in no small part due to the template system it uses.
That said, once implemented, it only takes 1 person who is knowledgeable in Linux to maintain the application, and a DBA to maintain the database(s) (if it isn't the same person). This is independent of scale, in no small part due to the template system it uses.
- Network monitoring.
- Server monitoring.
- Application monitoring.
- Synthetic user monitoring.
- Don't know if it is unexpected or innovative, but we use it primarily to cut down on known recurring issues before they cause outages.
- TBD - have not had it long enough to identify new ways to use yet.
- We want to use it to map our IT network.
- We want to use it to correlate issues to speed problem identification and time to resolution.
Yes
SolarWinds - due to cost of SolarWinds products
- Price
There was no other reason other than price.
I was not part of the evaluation or selection process, however, I do know that it was chosen due to price. They no longer wanted to pay for SolarWinds products. Why Zabbix was chosen over Nagios (another free option) is simply because it was easier to implement a trial with the prebuilt VM offered.
- Implemented in-house
Yes
First rolled out the server/database. Connected a few servers to ensure it was working. Then deleted the servers from the application and added proxy servers. Pointed the servers to the proxy and verified they started collecting data. Once setup was verified, started a staged rollout of agents to all servers for monitoring. Added Proxy servers as needed to spread out the load and to provide resiliency against network outages between sites. After server agent rollout started implementing website monitoring. Now we are starting to setup SNMP monitoring of Network devices.
Change management was minimal
Because we owned the servers the agents were being deployed to, we just needed to identify which servers were being added, and add them. No change management hassles were encountered. Though we did have issues due to our current design where many servers needed to be touched manually rather than a network deployment. This had nothing to do with change management, however, and everything to do with several M&A accquisitions that were not fully integrated with our network yet.
- Scaling the environment. If you don't know what you are monitoring, then it is likely you will not set up the templates correctly to scale the system efficiently. For us, that meant I have had to go back and restart many agents just to get them to pick up new or changed templates.
- Defining how you will monitor - How will you break down your host groups? By department? By application? By location? All of the above? Each of these works better if set up in advance, but for each implemented, you have exponential growth on the number and combination of templates to set up (at least if you are going to setup auto-registration, which is HIGHLY recommended for scaled deployments).
- Avoid automatic discovery or use with caution. Unless it is a very small or well-segregated environment, automatic discovery tends to discover more...fluff, than useful information. Further, after discovery, there is a lot of cleanups that typically must be done (naming each device, adding appropriate templates, etc.).