Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
F5 gtm support #8161
DO NOT DELETE THIS TEXT
If you would like to test this pull request then please run:
Adds discovery and polling of F5 GTM module Wide IP and Pools discovery.
Thanks for this. Before we review the code can you share some screenshots of what the various new pages look like please.
Could you also show the impact on poll time for your devices and indicate roughly how big they are? The f5 module already can have a big impact on users so we need to understand the risk to existing installs here.
In our environment we don't run GTM services on the same devices as we run LTM so for me it will have no impact on poll times on existing devices.
The code checks to see if the GTM module is running prior to discovering any new entities so I don't expect this will impact any devices that have the module disabled.
I'll leave these pre devices with this running for a few days so you can see what the data looks like (and that it's actually polling :) )
One thing i've been struggling with is how to handle representing a service that has multiple pools associated. In the end I decided that if I can sort out a way I can always add that later.
This is with a pre-prod devices with ~30 objects on it.
While on the main branch the discovery time and polling time is ~7s.
Polled in 7.028 seconds
SNMP [57/5.61s]: Get[19/1.41s] Getnext[0/0.00s] Walk[38/4.20s]
With the new additions discovery takes ~10s
SNMP [49/8.12s]: Get[11/0.87s] Getnext[1/0.07s] Walk[37/7.17s]
Polling takes ~8s
Polled in 8.377 seconds
SNMP [64/6.76s]: Get[19/1.40s] Getnext[0/0.00s] Walk[45/5.36s]
I'll leave it for a while to see if the problem comes back.
As a side note here is a comparison of LTM poling before and after the patch.