Skip to main content

API Checks - Trigger different alert state on certain assertions

Feature RequestAlerting

Since Checkly can do different type of alert states, it would be nice to have a different state for certain assertions you make on the response, not only related to response time.

A generic use case for this is a composite API request where you can have a response that is not complete or doesn't return the full information, only partial information.

For us, a practical use case is that we do have a multitude of 3rd party connections/integrations. We've built an endpoint to monitor these integrations and return a JSON array for each of the integrations. Some of the integrations have suboptimal fallbacks but it's a fallback nonetheless.
So in the case of one of the integrations fail but has a fallback we don't want such a severe alerting as "Fail" but rather a degraded notification, as this is something we want to look at but not as urgent as a full on failure that stops services from being used.

Thanks!

Posted by João Domingos ·
2 comments

Log in to comment and vote

Comments2

  • Rickard Borgmäster

    •

    Sep 8

    Definitely assertions on API would benefit a lot if they could be set whether to trigger a failure or a degraded alert. Lets say you use Checkly to poll a remote status API. The status API presents the working queue of a backend service. If the working queue is high there is a chance of SLA beeing missed or at least unhappy customers. So an assertion of queue=n where 0-50 is good, 50-100 is degraded and 100+ is fail, is what would be the implementation in checkly to represent the status and/or trigger alerts.

  • Tim Nolet

    •

    Jul 27, 2023

    Hey João, thanks for mentioning this. We are looking at improving some aspects of our alerting engine so this is valuable feedback