Bug ID 686675: Monitor's adaptive-limit is not restricted to a minimum of the adaptive noise floor

Last Modified: Feb 28, 2019

Bug Tracker

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

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 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.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4

Opened: Oct 02, 2017
Severity: 4-Minor

Symptoms

Setting an adaptive monitor's 'adaptive-limit' below the value of the db variable 'bigd.adaptive.default_noise_floor' behaves as though the limit is the same as the 'noise floor'. By default this is 100ms.

Impact

Monitor is still marked up even if the delay in the server's response is higher than the adaptive-limit configured for the monitor.

Conditions

Setting an adaptive monitor's 'adaptive-limit' below the value of the db variable 'bigd.adaptive.default_noise_floor'.

Workaround

Change 'bigd.adaptive.default_noise_floor' to be less than the desired adaptive-limit, or use an adaptive-limit larger than 100ms.

Fix Information

None

Behavior Change