Bug ID 1711109: Log throttling is non-deterministic

Last Modified: Nov 29, 2025

Affected Product(s):
BIG_IP_NEXT(CNF) CNF(all modules)

Known Affected Versions:
1.3.1, 1.3.2, 1.3.3

Fixed In:
1.4.0

Opened: Oct 30, 2024

Severity: 3-Major

Symptoms

Log throttling is non-deterministic, when large number of logs are being generated

Impact

May lose some logs when throttling is happening.

Conditions

-- Logs can be throttled, and users have no configuration mechanism to control this behavior. -- When a pool member, which is common to all pools (For example, 8 pools) changes state, each of the TMM threads will produce logs. Thus, a large number of logs are generated within a one-second interval. -- This results in mismatch condition of set/clear causing problem for alert monitoring.

Workaround

None

Fix Information

TMM allows a configuration variable `sys db`, which can be configured to the desired value. The newly introduced `sys db` variable is `log.tmm.global.throttle.rate` and the default value for this variable is 5

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips