Bug ID 565085: Analytics profile allows invalid combination of entities for Alerts setup

Last Modified: Oct 01, 2018

Bug Tracker

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

Known Affected Versions:
11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 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, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4

Fixed In:
12.1.0, 11.6.1 HF2, 11.5.4 HF3

Opened: Dec 30, 2015
Severity: 3-Major

Symptoms

When non cumulative metrics are selected for an Alert on a dimension that's other than a Virtual Server, errors appear in the log.

Impact

You are able to configure invalid alerts but no warning is given and the metric does not work and generates errors in the /var/log/monpd.log file.

Conditions

Analytics in use, and non-cumulative metrics such as the following are used on a time dimension: - Maximum TPS - Maximum Server Latency - Maximum Page Load Time - Maximum Request Throughput - Maximum Response Throughput

Workaround

None needed. This is Cosmetic.

Fix Information

Invalid combination of entities for Alerts setup is no longer allowed. Validation is present both on UI side and the backend.

Behavior Change