For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Ruggerfly1's avatar
Ruggerfly1
Icon for Nimbostratus rankNimbostratus
Jun 13, 2016

Request logging profile V11.5.3

Looking for best practices, or what's worked well on a logging profile: here's what I have in the template currently:   $DATE_NCSA F5=$BIGIP_HOSTNAME Source=$CLIENT_IP device=$User-Agent request=...
application delivery
LTM
Ryan_80361's avatar
Ryan_80361
Icon for Cirrostratus rankCirrostratus
Jun 14, 2016

Here's an example of what we use for the majority of our http/https virtual servers

client $CLIENT_IP:$CLIENT_PORT host.domain.com request $HTTP_REQUEST server $SERVER_IP:$SERVER_PORT
Ruggerfly1's avatar
Ruggerfly1
Icon for Nimbostratus rankNimbostratus
Jun 14, 2016
this is working well, but the separate lines to the logger is not correlating the request to the response. Is there a way to inject a session identifier so even on separate lines you can tie the response to the request? thanks