Bug ID 480995: APM client components are not using extended logging by default.

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP APM(all modules)

Known Affected Versions:
11.5.1 HF1, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.6.2 HF1, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
12.0.0, 11.6.0 HF4, 11.5.1 HF6

Opened: Sep 24, 2014

Severity: 3-Major

Symptoms

If end users of APM are encountering issues, extended client logs are disabled by default. This makes troubleshooting more difficult, and you would need to work with the end user to enable extended logging and try to reproduce the symptom they are seeing.

Impact

Extended logs are not present by default, which makes troubleshooting client-side issues more difficult

Conditions

This occurs for end users connecting to APM

Workaround

None

Fix Information

APM client components are now using extended logging by default.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips