Skip to content
This repository has been archived by the owner on Aug 4, 2023. It is now read-only.

More control over service degradations #293

Open
heipei opened this issue Mar 7, 2023 · 1 comment
Open

More control over service degradations #293

heipei opened this issue Mar 7, 2023 · 1 comment
Labels
alerting Triggering and sending alerts canny

Comments

@heipei
Copy link

heipei commented Mar 7, 2023

We receive frequent alerts due to alleged service degradation which can't be reproduced on our end. Our servers run in Germany (Hetzner, Falkenstein), and we perform checks using Frankfurt and other European regions. Sometimes we do receive degradation alerts from Ireland/Milan since the HTTP request took more than 3 seconds. These are always one-time incidents, the next check works fine, and we don't see slow response times in our access logs and almost never receive degradation alerts from Frankfurt.

It would be great if there could be additional thresholds for degradation alerts, e.g. only alert after three successive degradations were observed, or only if the degradation is observed from all regions simultaneously.

For now we're limiting the checks to only Frankfurt and Paris and enable double checks in order to hopefully reduce the amount of incorrect alerts we receive. Please let me know if you need more information.

@tnolet tnolet mentioned this issue Mar 24, 2023
@tnolet
Copy link
Member

tnolet commented Mar 24, 2023

@heipei we are looking at (way) more flexible alerting the coming quarters. I added this ticket to the overarching one. https://github.com/orgs/checkly/projects/4/views/4?pane=issue&itemId=21238722

@tnolet tnolet added the alerting Triggering and sending alerts label Mar 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
alerting Triggering and sending alerts canny
Projects
None yet
Development

No branches or pull requests

3 participants