Mar 27, 2026 - For details about updated CVE-2025-53521 (BIG-IP APM vulnerability), refer to K000156741.

Getting Started with iControl: Working with Statistics

In the previous article in the Getting Started with iControl series, we threw the lion's share of languages at you for both iControl portals, exposing you to many of the possible attack angles availa...
Published Jun 16, 2016
Version 1.0
devops
iControl
iControlREST
programmability
series-icontrol-getting-started
JRahm's avatar
Icon for Admin rankAdmin
Christ Follower, Husband, Father, Technologist. I love community and I especially love THIS community. My background is networking, but I've dabbled in all the F5 iStuff, I'm a recovering Perl guy, and am very much a python enthusiast. Learning alongside all of you in this accelerating industry toward modern apps and architectures.
View Profile
Joe_Pruitt's avatar
Joe_Pruitt
Jul 19, 2017

Hi JPV, through our APIs, the only historical stats we keep are in the high level performance graphs. I wrote an article on those APIs in this iControl 101 article.

 

The performance graphs are just for high level statistics. For object-level stats and states, you will have to write code to pull them down at your interval of choice using the various module APIs and store them locally. BIG-IP doesn't keep historical data for all configuration changes outside of audit logs which may or may not have all the information you need. We have our AVR reporting module that may help you get closer to where you want to go, but odds are if you are looking for granular specific historical changes, you'll need to build a polling system and collect the data yourself.

 

I'll dig a little deeper to make sure I'm not missing a feature but I'm fairly sure this is the way you'll need to go.

 

-Joe