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.
With Elastic Observability we can create alerts on all data we collect, such as logs, metrics, application services and synthetic monitoring. However, NetEye represents the main operational console from which to monitor the entire infrastructure. By sending alarms from Elastic Read More
Node export in the Tornado Processing Tree was broken on Firefox The bug was caused by a divergence between Firefox and Chrome in blob handling with CSP. Issue resolved, behavior is now consistent across both browsers. List of updated packages Read More
Processing Tree Rendering Issue We shipped a fix for a rendering bug in the Tornado UI Processing Tree. Under specific conditions, navigating back to the dashboard after expanding tree nodes caused the tree to render incorrectly nodes would appear collapsed, Read More
Role Search Now Works in Access Control We've fixed the search functionality in the Roles view under Configuration - Access Control, so you can now find roles instantly without any errors. List of updated packages To solve the issues mentioned Read More
Running Ollama locally or on dedicated hardware is straightforward until you need to know whether a model is actually loaded in RAM, how fast it generates tokens under load, or when memory consumption reaches a threshold that affects other workloads. Read More