Forum Discussion
Ruggerfly1
Nimbostratus
NimbostratusRequest 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=...
Ryannnnnnnnn
Altocumulus
AltocumulusHere'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
Ruggerfly1Nimbostratus
Nimbostratusthis 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