Bug ID 472782: A filter from the requests page that contains a predicate for "Violation ratings" will not work on the reports page

Last Modified: Apr 10, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP ASM, AVR(all modules)

Known Affected Versions:
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, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4

Fixed In:
12.0.0

Opened: Jul 23, 2014
Severity: 3-Major

Symptoms

When user configures a new filter on the Security > Event Logs > Application > Requests screen using the "Violation Rating" field (for example, "Violation Rating: At least 3"), that filter appears but does not work correctly on the Security > Reporting > Application > Charts screen, and it should.

Impact

Filter is not applied on ASM Charts page.

Conditions

Violation Rating filter is used in ASM Event Logs filters, and filter is loaded on the Charts screen.

Workaround

No workaround

Fix Information

When a user configures a new filter on the Security > Event Logs > Application > Requests screen using the "Violation Rating" field (for example, "Violation Rating: At least 3"), that filter now also works correctly on the Security > Reporting > Application > Charts screen.

Behavior Change