Last Modified: Sep 14, 2026
Affected Product(s):
BIG-IP AVR
Known Affected Versions:
11.5.4, 11.5.4 hf1, 11.5.4 hf2, 11.5.4 hf3, 11.5.4 hf4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 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, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.0.0, 12.0.0 hf1, 12.0.0 hf2, 12.0.0 hf3, 12.0.0 hf4
Fixed In:
12.1.0
Opened: Dec 30, 2015 Severity: 3-Major
When non cumulative metrics are selected for an Alert on a dimension that's other than a Virtual Server, errors appear in the log.
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.
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
None needed. This is Cosmetic.
Invalid combination of entities for Alerts setup is no longer allowed. Validation is present both on UI side and the backend.