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 IT Italy, 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 IT Italy, 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.
A safer way to run privileged Windows checks with SystemRunner If you’ve been monitoring Windows for a while, you’ve probably seen this pattern: some checks must run as LocalSystem (S-1-5-18), and the “quick fix” is to run the Icinga Agent Read More
This document describes the steps required to build, configure, and operate a Podman container based on php:8.2-cli, with the SNMP extension enabled, intended for executing monitoring plugins within a NetEye/Icinga environment. Pulling the base image podman pull docker.io/php:8.2-cli Containerfile for Read More
With the upgrade to NetEye 4.44, we've added a lot of new features (https://www.neteye-blog.com/2025/10/neteye-4-44-release-notes/) and, from my point of view, one of the most relevant is the introduction of Elastic Stack 9. This Elasticsearch major release (https://www.elastic.co/guide/en/elastic-stack/9.0/elastic-stack-release-notes.html) includes some new Read More
In NetEye, 'business processes' is a module used to model and monitor the business process hierarchy to obtain a high-level view of the status of critical applications. In short, they allow monitoring controls of individual components to be aggregated into Read More
If you've worked with Elastic APM, you're probably familiar with the APM Server: a component that collects telemetry data from APM Agents deployed across your infrastructure. But what happens when you need to segregate that data by tenant, especially in Read More