-
-
Notifications
You must be signed in to change notification settings - Fork 216
Replies: 2 comments · 6 replies
-
Do you mean they stay in
Tests are not marked as failed when the thresholds are breached. Only when we could not do the speedtest at all. Are the results marked as |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
|
Beta Was this translation helpful? Give feedback.
All reactions
-
This is the full log of the last result. |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
I was able to replicate the problem, at least the error above. Fixed it in #2702, please check when the next release it out. |
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 1
-
|
I will. Thank you. |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
Today I updated to the latest Docker image and now everything works perfectly. Thanks for your work. |
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 2
Uh oh!
There was an error while loading. Please reload this page.
-
Checklist
Deployment Environment
Docker Compose
Description
Hi, I’m confused about the behaviour of absolute thresholds vs the Benchmarking status.
In the UI it says:
“Absolute thresholds do not take into account previous history and could be triggered on each test.”
Based on this, I expected absolute thresholds to be evaluated immediately on each scheduled test.
My setup is:
Observed behaviour:
It seems that while the system is in Benchmarking, all threshold evaluation and notifications are suppressed, even for absolute thresholds.
Why?
Anything else?
No response
Beta Was this translation helpful? Give feedback.
All reactions