We rolled out some performance tweaks to resolve the delay in processing results. This should increase our processing capacity multiple times over. We will keep monitoring the situation.

At the moment, we are experiencing delays in processing check results. We are working on resolving the situation.

Stoked to announce some big updates to Checkly’s alerting features for 2019!

• First up is threshold based alerting. Using a dead simple menu, you can now set up exactly when, how and how often you are alerted. You can also set reminders just to be sure you don't miss out on any critical alerts.

Check out our docs for more information on how threshold alerting works.

• Next is the addition of 8 more data center locations! We made some changes to our infrastructure and can now offer all AWS regions as monitoring locations. 🇸🇪🇸🇬🇫🇷🇬🇧🇺🇸🇨🇦🇰🇷🇮🇪 here we come!

Hope you dig the updates!

Over the last 6 to 8 hours results from checks could have been delayed or missing. This issue hit some checks running in the us-east-1 and/or eu-central-1 regions.

You might have seen less results on your dashboard and noticed a time lag between results coming in.

Our alerting system runs separately from the storage and processing of results. Alerting was therefore not impacted.

This outage was caused by the rollout of a new check result and alerting system over the last 12 hours. More specifically:

• One daemon process was not tuned well enough to the amount of production traffic. Some messages per check run were delay ed and eventually discarded before being processed.

• Our de-duplication settings in our message queue were too strict. Some messages in the more busy regions were discarded at semi-random intervals.

These issues are now fixed and monitoring is in place. We are confident that this new system is much more robust and reliable now it is in place and working on production traffic.

For any questions please reach out to info@checklyhq.com

We are experiencing delays in processing API and Browser checks in the N. Virginia / us-east-1 region. Investigation is under way.

The browser check runner now used version 1.11.0 of the Puppeteer framework.

You can now click a button to move all query parameters from your URL into the dedicated query parameters table. This works especially great if you copy & paste in URLs from a cURL command or directly from a browser's address bar.

The button will pop up if there are any query parameters in your URL.

We just added a small improvement to the API checks builder. You can now toggle redirect following behaviour. By default, the HTTP request will follow any HTTP 3xx response, but in some cases you might not want this. Now you can switch that behaviour on and off.

Super happy to introduce two separate, but very closely related features to Checkly

1. Setup & teardown scripts

Tailor each HTTP request made by an API check to your exact situation. Write inline code, or reference a commonly used snippet.

• Setup scripts give you access to properties like the URL and headers of the HTTP request as well as all environment variables. Use cases are signing HMAC request, requesting tokens and setting up test data.

• Teardown scripts give you access to the response data, allowing you to read and modify the response. Use cases are cleaning up test data and scrubbing sensitive response data for regulatory reasons.

All scripts have access to popular Javascript libraries like moment, axios and crypto-js.

Learn more about setup & teardown scripts

2. Code snippets

Code snippets are reusable pieces of code that allow you to DRY ("Don't Repeat Yourself") up your Browser check script and your setup & teardown scripts.

Just use the partial notation {{> my_code_snippet}} to reference a code snippet in a browser check script. For API checks, just select a snippet from the dropdown.

Use cases are:

• Reusing common login routines in browser checks.
• Enforcing common setup or cleanup routines.

Learn more about using code snippets in browser checks

Between 08:00 20-11-2018 and roughly 16:10 20-11-2018 Chrome users could not use the interactive browser check runner in the browser create and edit pages.

This outage was due to a migration to new SSL certificates on the side of our our cloud hosting partner AWS, triggered by Chrome version 70 no longer accepting specific Symantec issued SSL certificates.

This outage did not impact the running of any browser checks, just the interactive part in the Checkly web UI. We migrated our backend to use the AWS web socket endpoints and all functionality has been restored.