Stats Profile tutorial?

Steven, if you ware looking at capturing bandwidth, how do you go about getting that information from within an iRule? The HTTP profile can help with the "HTTP::payload length" command but I don't think storing those in a stats profile is the best route here. Also, if you want to go that route, you'll have to code your iRule to batch up all the payload into a single buffer (in most cases requests will be sent in subsequent chunks and then processing by the backend servers when all chunks are sent. An iRule is a great place if you want to keep running totals, but building a reporting system with averages, max, etc is likely going to be tough as that data isn't readily accessible from within an iRule.

 

 

Generally we see customers go the iControl route (external management API) and build a separate application that gathers the statistics for the various objects they are wanting to report on. From the iControl API, one can get the total connects, bytes, etc. From there, one can calculate rates based on the difference over time of subsequent queries.

 

 

Now, if you want to do things like keeping track of of requests, etc, then an iRule is a great place. Just trying to build in rates (averages over time) will be difficult to do.

 

 

-Joe