Checkly changelog checklyhq.com

New

You can now sync your Browser Checks with JavaScript code from a GitHub repository! Just point your Browser Check to a file in your repo and Checkly will:

• Sync on commit. Just git push or merge your PR.
• Sync on deployment. Sync when a deployment is done. We can even run updated check code from your dev branch against a Preview environment.
• Include local dependencies. Any require of local helpers or config files are automatically included. No more Snippets!

This feature is now in public beta for all users. Private repos are only available on paid plans.

Read more in our docs or check out our own checklyhq.com repository and see how we dog food this feature.

To use this feature on a Private Location, make sure to update your Checkly Agent to version 1.0.6

Improvement

We just added the 2 minute, 2 hours, 3 hours and 6 hours options scheduling intervals for all API checks and Browser checks.

This should help you schedule your checks more efficiently.

This change is also available in our Terraform provider v1.6.2! and Pulumi provider v1.1.2

Note: if you are on an old pricing plan (marked DEPRECATED in your billing page) you will only see options from 10 minutes on. Get in touch with us over at support@checklyhq.com if you want to move to our new pricing.

Improvement

We just added two new labels to our Prometheus provider to help you slice, dice and chart your Checkly data in Prometheus and Grafana.

1. We added the group label, i.e. group="My group Name" to each checkly_check_status, checkly_check_degraded_status and checkly_check_result stanza.

2. We added the http_status_code label, i.e http_status_code="200" on all the checkly_check_result stanza for API checks, indicating the HTTP status code that was returned for the last check result.

This is live now for all accounts.

Improvement

When a maintenance window is active, we now display a small banner at the top so you aware that Checks are not running.

Note, during maintenance windows you can still run checks "ad hoc" with the Run Now buttons we have in various places.

This small enhancement was reported to our public roadmap

New

We just released the v1 of our Checkly Pulumi provider! This means you can now create and manage all your checks, groups, alert channels etc. using Javascript and/or Typescript.

Pulumi takes care of the syncing, team collab and all the process you are familiar with from your favourite Infrastructure-as-Code provider.

Install the Checkly provider from the Pulumi registry and check the examples we have in the public GitHub repo

New

You can now embed the response time and/or status of your API checks, Browser checks or even whole Groups in any Markdown page with two clicks. It looks just like this 👇

Just click the three dots menu on the home dashboard, check overview or group editor and click "Create Status Badge"

We are already using it on all our public repo's, like https://github.com/checkly/checklyhq.com

P.S. yes, it works fine with HTML or anywhere an SVG file can live

Improvement

A small improvement on the Friday. The Snippets page now shows the number checks that are using a Snippet. This makes it easier to remove any unused ones and keep your Snippet household tidy. O

Improvement

You can now proxy all check traffic through any HTTP proxy you might have in your internal network or private cloud when using Checkly's Private Locations.

Note: please update your Checkly Agent containers to version 1.0.5

• Just set your proxy address in the Private Location config
• API checks are automatically proxied
• Browser checks use the native proxy features of either Playwright or Puppeteer

Make sure to check our docs on how to effectively use HTTP proxies across your full Checkly setup.

Improvement

Private Location health is now shown in the private locations list under account settings. The health indicators let you know whether all of your checks are running in the private location or if the location has capacity issues or failures causing checks to be delayed or fail to run.

Private location queue health metrics are also available in the REST API and the Prometheus integration so you can monitor and act on them from your own systems.

Improvement

You can now use the standard Node.js require() syntax to import code snippets into your Browser checks, where we first only supported Handlebars templates.

Here's an example:

1. Create a login routine you want to reuse in Browser check scripts. Export it as a function

2. Now require the snippet from the ./snippets directory — just like JS file — and call the function passing in the relevant parameters.

Read more in our docs on how to use this new syntax.

This is now the recommended way to DRY up your code. The legacy Handlebars notations is still usable till further notice.