Bug ID 459294: log publisher configuration is required when global log throttling limits are set

Last Modified: Oct 17, 2023

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

Known Affected Versions:
11.6.0, 11.6.1, 11.6.2, 11.6.3,,,,, 11.6.4, 11.6.5,,,, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 12.1.3,,,,,,,, 12.1.4,, 12.1.5,,,, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Opened: Apr 28, 2014

Severity: 4-Minor


When the global log throttling rate limit is configured using the "global-network" logging profile, you might not see log drops reported through the period dropped digest log message. No configuration warning is provided to the user when the log publisher is missing from the log profile, whenever rate limits are set.


Log message drops due to log throttling rate-limits are not reported through a periodical log dropped digest message.


This happens in the specific case, when log publisher configuration is missing in "global-network" log profile and when log throttling rate limits are set. Without a valid log publisher, the notification of log drops due to log throttling is not possible.


Define a valid log publisher when configuring global log throttling rate limits.

Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips