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=...
Ryan_80361
Cirrostratus
CirrostratusHere'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
Ruggerfly1would this capture and log something like this? POST /Microsoft-Server-ActiveSync?Cmd=FolderSync&User=fakename&DeviceId=v140Device&DeviceType=SmartPhone HTTP/1.1 then in the Response Template I would log the HTTP_STATUS thanks!- Ruggerfly1Update - this captured the entire ActiveSync request with User, device, now waiting to see if the HTTP_STATUS from the response is correlated Request Template $DATE_NCSA ${Host} ${User-Agent} Source=$CLIENT_IP request=$HTTP_REQUEST Response Template $DATE_NCSA ${Host} Response HTTP_STATUS code HTTP_STATCODE
- Ruggerfly1this 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
- Ruggerfly1Last update - completed - this config sends the Full request and full status to correlate Request: $DATE_NCSA ${Host} ${User-Agent} Source=$CLIENT_IP request=$HTTP_REQUEST Response: $DATE_NCSA ${Host} $HTTP_REQUEST Response=$HTTP_STATUS
