Skip to main content

Fire alerts from Triggers

Feature RequestCLI

Currently there's no way to programmatically (via CLI or API) trigger/run existing checks and have them fire alerts on failure. We have a set of pre-production checks that we don't need running at any regular cadence (we set them to 24 hours for now) but we trigger them as part of our CI/CD pipeline. We'd like for them to trigger the alerts we defined for those checks even if they're triggered via the CLI. Since this would be a behavior change there probably needs to be a way to opt-in like --fire-alerts. Basically we'd like to replicate the functionality that only exists in the UI to "Schedule Now" but via the CLI.

Posted by James Hartig ·
Status: Completed8 comments

Log in to comment and vote

Comments8

  • Hervé Labas

    Team•

    Jul 27

    Hi all,

    We release a checkly checks run command as part of 8.18.0 that will act like the “Schedule Now” button from the Checkly Webapp and trigger alerts if any.

    It’s different from trigger and test which come with different options.

    Documentation

  • Laura Guo

    •

    Jul 27

    •

    Merged request

    •

    2 votes

    Add ability to schedule check runs via the Checkly CLI

    Currently, we can run checks with checkly test and checkly trigger, but these only create test sessions.

    It would be helpful to have a checkly schedule command or similar that acts like the “Schedule Now” button in the UI, to run deployed checks and show the result in the check run history.

  • Tim Nolet

    •

    Apr 4, 2024

    Hey James, thanks for submitting this. We get this question now and then and we have always made a "hard split" between triggering alerts for monitoring and testing use cases. The reason is that many of our users have quite extensive on-call setups via Pagerduty integrations and the like. It would be very annoying if an on-call team in timezone X gets paged because a dev in timezone Y just ran a test session on a dev or staging account.

    Our recommended solution is to have your CI/CD pipeline fail have its notifications options trigger any messages. We do this ourselves for our CI/CD for our app and www projects. In our case we send a Slack message to a dedicated channel.

    I do understand your request BTW, so I will tag your request accordingly. An extra flag would indeed be most useful here.