Bug ID 977609: Request logging profile not logging server-side variables on a virtual-server with rate-limit or connection-limit applied

Last Modified: Nov 22, 2021

Bug Tracker

Affected Product:  See more info
BIG-IP TMOS(all modules)

Known Affected Versions:
13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 16.0.0,, 16.0.1,,, 16.1.0, 16.1.1, 16.1.2

Opened: Dec 30, 2020
Severity: 3-Major


Pool-name, server IP address, and port are missing in the syslog message.


The request logs are intermittently missing information for VIRTUAL_POOL_NAME, SERVER_IP, SERVER_PORT.


This occurs when the following conditions are met"=: -- The virtual server is configured with Request Logging that is configured with a logging template similar to the following: Request Logging template using '$VIRTUAL_POOL_NAME', '$SERVER_IP', '$SERVER_PORT'. ltm profile request-log with: request-log-template "Virtual: $VIRTUAL_NAME Pool: $VIRTUAL_POOL_NAME Server IP: $SERVER_IP Server Port: $SERVER_PORT" } -- The virtual server is configured with rate-limit.



Fix Information


Behavior Change