Zabbix

We monitor Virtual network functions (VNFs) alarms & performance graphs on Zabbix. It is basically an FM & PM system that collects data from all the nodes & aggregates them in the form of user-readable graphs & XL sheets. It is also used to set performance-based alerts in the system & it can also be used as an aggregator for a big NMS type system like Nokia's NetAct.

Zabbix is the complete monitoring tool that can monitor any type of environment, We are monitoring Amazon-hosted EC2 instances and also Azure Virtual machines. Zabbix is very active in communicating with its agents. This tool is open-source and can be deployed on any Windows/Linux-based machine. We are monitoring more than 200 servers including the websites and windows services.

We're using Zabbix for almost 4 years now to monitor some specific servers and applications in our South America (+Portugal) sites.
It is configured to run discovers on our vCenter to grab any new VM and to start monitoring its CPU, Mem, Disk usage, etc. For specific applications, those more critical to the business, we create templates to monitor the services.
We have also created some tests using CURL to authenticate to applications and measure the end-user experience, so we can generate alerts when an important application is taking more time than it was supposed to authenticate.
It also has a great 'SLA' dashboard, where you can see the amount of time that an specific application was out-of-service during a period of time. We use it to provide some evidences to the business. Those applications can be constituted by multiple servers, services, databases, etc... It is very flexible on this level.

I use Zabbix to monitor our infrastructure, network, services and applications.

As an open-source monitoring solution, Zabbix is our preferred choice. Our company has been using it since 2017 to monitor all infrastructure. The overview we get from it is fabulous. It's immediate and it provides very clear information on many levels depending on what you want to see based on user roles and permissions. You can configure absolutely everything you can image with it.

Zabbix is currently one of our main monitoring applications (next to Munin). It is used to monitor the state of hardware (temperatures, hardware-errors), the state of the operating system (running, load, memory usage, etc.) and the state of services (running, network-connections, load, etc.). Additionally, some services can report on further metrics, e.g. if files are outdated or show unreasonable behavior. Through the trigger-framework, we can start automated mitigation, as well as manually inspect the issue.

We use Zabbix to monitor network assets and customer links to generate reports and resolve potential problems in its infrastructure.

In the beginning, we started using Zabbix in a small deployment, running the Linux box, deployed as a docker container. As we got familiar with the infrastructure, we decided to start using to basically monitor some servers. As we got confident, we started to monitor all the servers on-premise and some servers on a private cloud and finally, we included the network assets. Currently, it's been used just by our IT department and our main goal is to have a tool capable to monitor and early detect infrastructure issues to act as quick as possible.

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.

We use Zabbix to monitor both the internal IT Infrastructure, as well as the external IT Infrastructure. It was first implemented in 2010 and it has evolved significantly over the years, giving us a single pane of glass for monitoring systems, storage, network and the applications themselves. By implementing a solution that provides us this level of visibility, Engineers only have a single place to look to find the root cause of an issue, rather than jumping from system to system, trying to correlate events.
Zabbix is heavily used by Systems, Network and Database Engineers as well as Applications Developers to provide visibility to what is happening in the environment, to notice a problem before our users do.
We have implemented Zabbix so that there is a central Zabbix server (hosted in AWS), with Zabbix proxies at each physical location where there is infrastructure. This way if the Zabbix server goes down, no data is lost, as it is cached on each of the proxies until connectivity is restored to the Zabbix server.

We are big fans of Zabbix and use it as our core monitoring system for our Chinese MSP business, monitoring thousands of hosts for hundreds of customers across dozens of locations, data centers, and cloud. We've customized it with some UI enhancements, API additions, and DB integrations into ticket and service systems, too.

While working at the Comcast headquarters as a Linux Engineer on their Splunk team, I set up Zabbix to monitor approximately one-thousand (1,000) physical servers running Splunk. It allowed us deeper insight into the use and performance of Splunk throughout our infrastructure. It also gave us the ability to prevent small problems (such as hard drive failures) from growing unchecked and leading to serious outages.

Zabbix is a simple to setup and easy to manage solution. Very little in-depth tech skills needed to deploy initially due to pre-made ISOs and virtual machines, and with the help of a raft of templates available for free online to make it an essential monitoring tool for any business. Support is available if you want it - although from my perspective it looked to be costly if you simply want light email only assistance on your setup.

We use Zabbix organization-wide to monitor several environments in AWS. Use of the Zabbix proxy allows us to manage many environments from a centralized location. We can graph and alert on all separate environments in a monolithic fashion. Zabbix's new trending and forecasting allow us to model performance based on trends in each environment.

It's used across the whole organization. It's used to monitor the server parameters, application URLs, logs etc.

Zabbix is being used for data collection and monitoring sections of our network. We use its information to plot out future resource bottlenecks, plan hardware upgrades, identify unusual usage patterns, failure rates, uptimes and execution of maintenance scripts.

Our operations team uses Zabbix to monitor our company's physical and virtual infrastructure. Zabbix monitors our servers, network gear, CPU performance data and application uptime. We have integrated Zabbix alerts with PagerDuty to get pinged when an issue arises.

The company was using a very old version of Nagios at the time. I created a pro/con list for my manager on which monitoring application to switch to. Zabbix ended up being the winner based on features. It is specifically used to monitor EMR servers to ensure they are readily available for Office use at all times. We also used the software to notify support staff if there is an issue. The on-call person will receive the alarm and solve it as needed.

Zabbix is used to monitor about 5000 network devices, 1000 servers and other services totaling 8000 hosts. Our IT department is deploying Zabbix to replace older monitoring services, to expand and modernize monitoring and alerting. Alerting is being automated and alerts are to be distributed to the responsible parties and even automate recovery where possible. Zabbix also stores a lot of useful "normal state" performance metrics for reference during problems.

Zabbix is a preferred option for our organization based on its open-source nature and versatile functionality. The Zabbix sender and trap features allow us to set up adhoc alerts based on specific criteria, such as log grepping for error frequency. We also use Logstash in tandem with Zabbix to generate alerts based on Logstash queries.

Zabbix is currently in place monitoring servers and network hardware across the entire organization. We're using it to monitor service availability as well and have made attempts to use it for hardware monitoring as well, but the SNMP Trap support is lacking at best and very clunky to implement.