Bug ID 554626: Database logging truncates log values greater than 1024

Last Modified: Apr 10, 2019

Bug Tracker

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

Known Affected Versions:
11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8

Fixed In:
12.1.0, 11.6.1, 11.5.4 HF2

Opened: Oct 27, 2015
Severity: 3-Major
Related AskF5 Article:
K14263316

Symptoms

The Logging agent truncates log values greater than 1024. If the log value size is greater than 4060, the field is empty or null.

Impact

The reporting UI displays null or empty fields when the logged value is too large in size, such as a huge session variable.

Conditions

Logging into local database with log values (such as session variables) greater than 1024. If this size is too high (greater than 4060), the field displays as empty or null in reports.

Workaround

No workaround.

Fix Information

This release handles large single log values.

Behavior Change