Bug ID 424592: Request logging not logging pool name with APM

Last Modified: Sep 27, 2019

Bug Tracker

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

Known Affected Versions:
11.2.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.4, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 15.0.0, 15.0.1

Opened: Jul 03, 2013
Severity: 3-Major
Related AskF5 Article:
K71220204

Symptoms

Pool name is not being logged when access profile is attached to the virtual.

Impact

Pool name is not being logged most of the time.

Conditions

1. Create a pool for syslog server called "syslog-pool" 2. Create a request logging profile like the following: ltm profile request-log reqlog-pool { app-service none defaults-from request-log response-log-pool syslog-pool response-log-template "Path is $HTTP_PATH, Pool is $VIRTUAL_POOL_NAME" response-logging enabled } 3. Attach it to an HTTP virtual server with a valid default pool. 4. Send some requests and observe the path and pool are logged. 5. Create an access profile. Edit access policy to be "Start -> Allow". 6. Attach it to the virtual server.

Workaround

This issue has no workaround at this time.

Fix Information

None

Behavior Change