Checkly changelog checklyhq.com

You can now filter events on the global and per check event timelines.

This is super useful when you have a busy account with multiple outages or degradations overlapping each other, or you just want to look at your deployment events.

You can filter by:

• Failures
• Recoveries
• Degradations
• Deployments

We just added groups to our Reporting beta. You can now

• see your checks organized by group just like in the home dashboard.
• access the group name in the CSV export

Have a look at https://app.checklyhq.com/reporting

One of our most requested features — Reporting — is now launched in beta! Check

• Evaluate and visualize trends over longer time windows.
• Export your data as CSV

We wanted to ship this as early as possible, so let us know what works and what doesn't.

We just released a new integration and some small UX features:

1. You can now filter your dashboard for checks that failed in the last 24 hours, giving you a quick overview which checks might be passing right now but had an issue in the last day.

2. We now integrate with incident management solution Spike.sh. Spike is an up & coming alternative too Pagerduty, Opsgenie etc. Our docs show how to get up and running in 2 minutes.

3. Our code editor got some extra keyboard short cuts and DX 💕. You can now:

• use CMD+/for (un)commenting lines. This is Shift+/ on Windows.
• use TAB to actually add tabs…

Last but not least, you can now enable Vim or Emacs mode and use commands like:

• dd to delete a line
• gg to go the first line of your script..
• or SHIFT+g to go to the last line

You can now use the standard process.env.VARIABLE notation to read variables in all scripts. We already supported that for Browser check scripts, but not in setup & teardown scripts for API checks.

The old environment object still works, but we advise to use process.env from now on. A short example.

Earlier you needed to read any variables from the proprietary / non-standard environment object, e.g.

// a setup or teardown script
const key = environment.API_KEY

Now you can just do

// a setup or teardown script
const key = process.env.API_KEY

This should help with local debugging!

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.