Checkly updates checklyhq.com

We just shipped some nice UX improvements to our webhook editor!

• Full syntax highlighting for easier templating
• Autocomplete for variables and template functions available in the context of a webhook

Happy webhooking!

Hi,

Today we deprecate our legacy SSL alerting completely. This means if you want to receive SSL expiry alerts on any of your alerting channels you have to enable this on at least 1 one channel!

1. If you see a lock icon with a number off days in the alert types in your alert settings, you're already good!

2. If you just see greyed out lock icons, then pick the alert channel you want to receive SSL expiry alerts on and enable the SSL alert type:

We just launched a set of new integrations! 🙌

• Microsoft Teams: Receive failure, recovery, degradation and SSL alerts.
• Splunk On-Call (formerly VictorOps): Open & close alerts automatically.
• Discord: Receive failure, recovery, degradation and SSL alerts.
• GitLab Alerts: Open & close alerts automatically.

Read all about how to install and use these new integrations on our docs/integrations page or just head over to your alert settings to add these new alerting channels.

Just before we go into the holidays we added two small improvements to Checkly — of course all based on customer feedback!

1. Transfer account ownership

You can now transfer the owner role to a team mate straight from the UI. Just head over to the team tab and hit the "transfer ownership" button.

2. Webhook variables for API check response

You can now report the response status code and status text for API checks in your webhooks. We exposed both data items respectively as the API_CHECK_RESPONSE_STATUS_CODE and API_CHECK_RESPONSE_STATUS_TEXT variables. Use them in your webhooks as follows:

{
  "statusCode": "{{API_CHECK_RESPONSE_STATUS_CODE}}"
}

We saw elevated error rates on scheduling checks in ap-southeast-1 region between November 24, 2020 15:24-16.05 UTC and November 25, 2020 3:08-6:57 UTC. This should have not affected our customers and their checks must have simply scheduled at another location. The underlying cause is in our upstream cloud provider.

We will perform some necessary database maintenance today 12-11-2020 at 12:00. This will result in some downtime for the web app and the underlying API. We estimate the maintenance will take ~1 minute.

3 weeks ago we notified all existing Checkly customers we were making a subtle but important change to how we assert JSON array responses.

This change was just pushed to production some minutes ago at 13:00 CET

What is the change in a nutshell?

We are changing how JSON responses with arrays are handled when doing assertions on those arrays. Get the full story in this blogpost

We saw elevated error rates on scheduling checks in multiple regions from 11:30 to 12:00 PM CET. This could have resulted in failed checks. The underlying cause is in our upstream cloud provider. We do not have a root cause yet.

The situation seems to have resolved at roughly 12:00 PM CET. We are monitoring the situation.

Update 01:00 PM: Upstream provider is stable in all regions for the last 30 minutes. We consider this incident closed but will monitor stability as normal.

The Checkly Terraform Provider now supports snippets and Terraform v0.13.

Since today, the Terraform Provider is also available through the official Hashicorp Provider Registry!

Hi,

We just shipped two improvements to existing features:

1. Filter GitHub deployments

You can now filter your GitHub triggered deployments using regular expressions in the CI/CD integrations tab.

When would you use this?

1. You can now only run checks / check groups on the Preview or Production environment
2. You can now only run checks / check groups for a specific project in your mono repo. This works great with Vercel's recent mono repo feature

2. Access tags in webhooks

All tags assigned to your checks are now available as the environment variable {{TAGS}} in your webhook templates. This way you can use tags to trigger routing decisions on your webhook integration.

We have an example on how this works in our docs