Bug ID 935293: 'Detected Violation' Field for event logs not showing

Last Modified: May 29, 2024

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

Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 16.0.0, 16.0.0.1, 16.0.1

Fixed In:
16.1.0, 16.0.1.1, 15.1.3, 14.1.4, 13.1.3.5

Opened: Aug 11, 2020

Severity: 4-Minor

Symptoms

Violation is missing/details not populated in the event log page, when a POST request with large number of parameters are sent to the BIG IP system.

Impact

You cannot see the violation details.

Conditions

-- A large POST request with lots of parameters is sent to BIG-IP system. -- 'Learn New Parameters' is enabled.

Workaround

Disabling parameter learning helps. Note: This happens only with a large number of parameters. Usually it works as expected.

Fix Information

The eventlog is reserving space for violations.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips