Logging load balancer decisions

If I may add, there's a few things to consider:

• For things like client request and server response, you can certainly write an iRule that spits these out to local (or remote) syslog, or if you're running an F5 version that includes the Request Logging profile, that could be, by far, the easiest way to go.

http://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/bigip-external-monitoring-implementations-11-3-0/1.html?sr=31972321

• There's no specific log metric for load balancing algorithm that I know of, but you could at least see which server node was chosen using the LB::server addr command in an iRule. Here's an exmaple:

  when LB_SELECTED {
      log local0. [LB::server addr]    
  }
  

That of course is overly basic and doesn't include any real context. Have a look at the LB::server wiki page for more information:

https://devcentral.f5.com/wiki/iRules.LB__server.ashx

• You probably have a little more leeway with universal mode, as that generally requires an iRule to assist in the persistence. Can you please post your universal persistence iRule? There should be a way to insert additional tracking information.

• The LTM logs, where you'll see most of this information, is at /var/log/ltm. You can see that log in the management GUI under System - Logs - Local Traffic, or if you want to see what's happening in real time, open a shell to the management interface (console or SSH) and execute the following command:

  tail -f /var/log/ltm
  

• If you intend to capture client requests, server responses, persistence information, and more, you're going to find that local syslog will become an unsuitable solution very quickly. I highly recommend investing in a remote syslog server (ie. free Linux variants or commercial products) and enabling High Speed Logging on the LTM.