After deploying and configuring F5 network gear in your company, your next step will be to monitor these new devices.
Depending on your monitoring solution, integrating your F5 network equipment can range from simple to complex.
Maybe you need to search around for the various MIB files to get the optimal monitoring parameters, or perhaps you have to search on the internet for plugins or templates for your F5 devices.
Not so with our NetEye solution.
With the NetEye implementation you can easily use the attached file archive that contains the service profile for F5 and the necessary plugins.
This service profile contains the most important monitoring checks for F5 devices:
Disk Space (This check monitors the available space on the F5 hard disks)
CPU Usage (This check measures the CPU utilization of the F5 devices and loads this information into InfluxDB so you can view it on a dashboard in Grafana)
Failover status (This check monitors the cluster status of the F5 infrastructure)
Pool Member Status (This check monitors the status of individual pool members)
Sync Status (This check monitors the status of F5 device synchronization)
Hardware Status (This checks monitors the hardware status of the F5 appliances)
Interface Table (This check monitors the network ports, their status and the traffic on the ports)
Uptime (This check indicates the elapsed time since the last reboot)
First of all, you need to copy the plugins from the tar archive file to the NetEye plugins directory.
Afterwards, you can simply load the attached service profile by using Architect Monarch in the NetEye Configuration section.
After that, you have to set the correct SNMP authentication on the loaded service checks.
Finally, you can assign this newly loaded service profile to your F5 network devices and start monitoring them.
I started my professional career as a system administrator.
Over the years, my area of responsibility changed from administrative work to the architectural planning of systems.
During my activities at Würth Phoenix, the focus of my area of responsibility changed to the installation and consulting of the IT system management solution WÜRTHPHOENIX NetEye.
In the meantime, I take care of the implementation and planning of customer projects in the area of our unified monitoring solution.
Author
Tobias Goller
I started my professional career as a system administrator.
Over the years, my area of responsibility changed from administrative work to the architectural planning of systems.
During my activities at Würth Phoenix, the focus of my area of responsibility changed to the installation and consulting of the IT system management solution WÜRTHPHOENIX NetEye.
In the meantime, I take care of the implementation and planning of customer projects in the area of our unified monitoring solution.
Scenario NetEye 4 is a comprehensive monitoring platform which natively supports Business Processes. A Business Process is an abstract view of a customer’s business from the Application point of view. Usually, it’s a collection of Icinga 2 checks aggregated by Read More
On February 3rd and 4th, 2024, we attended FOSDEM, a major event where thousands of free and open-source software developers from around the world gather to exchange ideas and collaborate. This year I dedicated much of the second day to Read More
Introduction: Unveiling Elastic APM in Containerized Environments In today's dynamic digital landscape, where every interaction matters, understanding the intricacies of application performance has become paramount. Elastic APM is a powerful toolset within the Elastic Stack included in the NetEye SIEM Read More
In this article, we’ll explore how to configure the “Agent Binary Download” setting and set up your own artifact registry for binary downloads within a NetEye cluster. Prerequisites Before we begin, ensure you have the following prerequisites in place: Your Elastic Agents Read More
We fixed the following issues in the integration between NetEye and Alyvix. Test Case file selection dropdown We fixed an issue in the Test Cases view for which, when switching between the Test Cases of different nodes, the wrong Test Read More