Bug ID 535119: APM log tables initial rotation in MySQL may be wrong

Last Modified: Oct 06, 2020

Bug Tracker

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

Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4

Fixed In:
12.1.0

Opened: Jul 25, 2015
Severity: 3-Major

Symptoms

APM uses local MySQL to store logs and automatically rotate the log tables when the log table size exceeds a limit, which removes the oldest log table and make room for a new current log table. However, the initial timestamps of those log tables may be very close--or the same in 1-second granularity of MySQL timestamps--right after the installation that initially creates those log tables. Due to the timestamp granularity, it may be wrong for APM to choose the oldest log table to remove in the first round of rotation, resulting in removal of log data that are not the oldest. After the first rotation, the log table rotation should work as normal.

Impact

Log data that are not the oldest may be removed at the first round of log table rotation.

Conditions

The first round of log table rotation after installation

Workaround

None

Fix Information

At log table initialization, add extra 1-second gaps between the times to create individual log tables, to avoid the problem of 1-second granularity in MySQL timestamps.

Behavior Change