Unexpected low load alert not working as expected

[DamianG]

We have "Unexpected low load" alerts and we think alerting is not working as expected because some alerts are raised when de load of a request is not reaching the thresholds set. E.g:

• Settings:

Does this configuration means that an alert will be triggered when traffic decreases 90% (or more) than expected during 15 minutes? This means, an alert will be triggered if there is  only 10% (or lower) than expected?

• Example: an alert was raised when the is traffic is not zero and with no significant changes:

If we do a comparison:

   - 2 hours before:

   - 1 day before

    - 1 week before:

The key here is that 3 weeks ago I changed the settings from 80% to 90% and now I'm getting more alerts than before.

Is this behavior correct?

Thank you.

[jcimera]

I was wondering how the Service load drops settings work too.    I don't understand the "Alert if the observed load is less than this percentage of the expected value" settings.    We have these set to 100%.    If the load is less than 100% of the expected value it would alert if the load was less than 0.    However,  we are getting Unexpected low load alerts showing a decrease to 130 requests/min as an example.   I have not found any good documentation explaining this alert.

[Mizső]

Hi @jcimera 

"Alert if the observed load is less than this percentage of the expected value".

Example: your service has 100 request / min load at morning (Davis learned this behaviour). Your expected load eg. 90%. If load is dropped below the expected value 90% for a configured timeframe problem will be opened (eg. 80 request / min for 10 min).

I hope it helps.

Best regards,

János