Improvement

We just released Runtime 2022.02 with Playwright 1.20.2 and Puppeteer 13.7.0 among other NPM package updates and additions.

Runtime 2022.02 is the new default for all new users, existing users should upgrade in due time. You can do this upgrade in a controlled fashion. Read more on how runtimes work and how you can gradually upgrade your account in our documentation. — It's just one click.

New

The revamped Check Overview page now gives you more ways to dive into data that matters for your checks, and your business.

Here’s what you can do now:

• Easily access a timeline of all individual check runs.
• Constraints-free: see alerts, check runs and other data for any time interval you need.
• Integrating Checkly with your CI/CD – as you should? Access those check runs more easily than before.
• There’s more… 👇

Read more on our blog.

Improvement

All tags you set on Checks and Check Groups are now propagated to your Opsgenie integration.

Use tags to route alerts to specific teams or trigger specific actions. This feature enhancement came from our Public Roadmap.

New

We moved our public API to General Available. What does this mean?

• Updated documentation and API playground.
• New, non-polymorphic endpoints for creating checks
• Two deprecated endpoints (see below)
• A million — well, *checks bug tracker* 38 actually — fixes to docs, schema's, default values, and response bodies.
• Rate limiting on endpoints to prevent abuse.

Hundreds of devs are already using our API daily through our Terraform provider, Pulumi provider (in preview) or directly from their codebase.

P.S. the auto-generated OpenAPI / Swagger docs are still available at https://api.checklyhq.com

Deprecated endpoints

We deprecated two endpoints on our public API as part of making the public API Generally Available.

• GET /check-results-rolled-up. This endpoint was a stop-gap for longer-range data. You can now use the regular /check-results endpoint

• POST /checks. This endpoint was polymorphic. We now have dedicated endpoints for API and Browser check creation on /checks/api and /checks/browser

We will remove these endpoints on Monday 4 July 2022. We will follow up with emails to alert you as we near that date.

New

We just started a tech preview of our Pulumi provider. This provider allows you to use your favourite programming language to manage your monitoring setup from your code base!

This integration is now in preview and we are actively looking for early adopters. Just drop a short email to support@checklyhq.com if you want to be involved in the preview and we will gladly help you get started.

Improvement

Last week we released a set of updates for our public API to give you even more access to your data.

1. You can now access all alerts through the new /v1/check-alerts API endpoint. Use it to generate custom reports on how many outages you had, or integrate into a custom dashboard.

2. For Browser checks, you now have full access to trace summary data (like web vitals and error counts) and assets like screenshots. Next to this, you have access to the full job log for both API and Browser check types.

Here is an abbreviated, Browser check example fetched from the /v1/check-results/{checkId}/{checkResultId} endpoint.

Notice…

1. The assets property. It's an array with links to assets stored on S3.
2. The browserCheckResult.pages property holds the web vitals collected per page visited in your script
3. The jobLog property which holds the log as a structured array.

{
    "id": "28b4d8f7-xxxx",
    "hasErrors": false,
    "hasFailures": false,
    "runLocation": "us-east-1",
    "startedAt": "2022-02-08T10:00:56.058Z",
    "stoppedAt": "2022-02-08T10:00:58.032Z",
    "responseTime": 1974,
    "apiCheckResult": null,
    "browserCheckResult": {
        "type": "PLAYWRIGHT",
        "pages": [
            {
                "url": "https://www.checklyhq.com/",
                "webVitals": {
                    "CLS": {
                        "score": "GOOD",
                        "value": 0
                    },
                    "FCP": {
                        "score": "GOOD",
                        "value": 354.5
                    },
                    "LCP": {
                        "score": "GOOD",
                        "value": 436.5
                    },
                    "TBT": {
                        "score": "GOOD",
                        "value": 67
                    },
                    "TTFB": {
                        "score": "GOOD",
                        "value": 92.20000000018626
                    }
                }
            }
        ],
        "errors": [],
        "endTime": 1644314458031,
        "startTime": 1644314456059,
        "traceSummary": {
            "consoleErrors": 0,
            "networkErrors": 0,
            "documentErrors": 0,
            "userScriptErrors": 0
        },
        "runtimeVersion": "2021.10",
        "jobLog": [
            {
                "time": 1644314456057,
                "msg": "Starting job",
                "level": "DEBUG"
            },
            {
                "time": 1644314456057,
                "msg": "Compiling environment variables",
                "level": "DEBUG"
            },
            {
                "time": 1644314456058,
                "msg": "Creating runtime using version 2021.10",
                "level": "DEBUG"
            },
            {
                "time": 1644314456059,
                "msg": "Running script",
                "level": "DEBUG"
            },
            {
                "time": 1644314458032,
                "msg": "Run finished",
                "level": "DEBUG"
            },
            {
                "time": 1644314458235,
                "msg": "Uploading screenshots",
                "level": "DEBUG"
            },
            {
                "time": 1644314458235,
                "msg": "Job finished successfully",
                "level": "DEBUG"
            },
            {
                "time": 1644314458235,
                "msg": "Uploading log file",
                "level": "DEBUG"
            }
        ],
        "jobAssets": [
            "https://s3.us-east-1.amazonaws.com/fn-screenshots-us-east-1-prod/b7bf6461-73df-xxxx/f951a5d4-xxxxx_1644314454020_us-east-1_screenshot.jpg"
        ]
    },
    "checkId": "f951a5d4-xxxx",
    "created_at": "2022-02-08T10:00:58.664Z",
    "name": "https://checklyhq.com",
    "checkRunId": 1644314454020,
    "attempts": 1,
    "isDegraded": false,
    "overMaxResponseTime": false
}

Improvement

You can now skip the SSL certificate validation for API checks by enabling the "Skip SSL" checkbox. Before, API checks would always fail against endpoints with non-valid SSL certificates.

This comes in handy when working on a dev environment with a self signed SSL certificate, or testing against a staging environment with a SSL certificate you let slip past the expiration date.

Note: this is does not impact Checkly alerting you when SSL certificates are about to expire

Improvement

If you have users and customers in and around Indonesia, we have great news: We've added a new data center location. You can now run your checks from the Jakarta region.

We'll continue to add new regions as they become available.

Improvement

You can now use code snippets in inline setup & teardown script for API checks.

Before, we had hard split:

1. Either you run exactly one snippet, select by the snippet name
2. Or you code it yourself per check. No snippets allowed.

With this improvement, you can now compose your snippets, providing custom behaviour, while still benefiting from the DRY principle of single source snippets.

Improvement

You can now access the environment name and deployment ID in your checks when triggered by a deployment. It joins the already available environment url

You can use this info in your browser check scripts and/or setup & teardown scripts to make decisions on what environment you want to test against.

You access these variables with the familiar notation

• process.env.ENVIRONMENT_NAME new
• process.env.DEPLOYMENT_ID new
• process.env.ENVIRONMENT_URL

These environment variables are populated based on the trigger provider. For example, when our Vercel integration triggers a check run on a preview, you will the following:

• ENVIRONMENT_NAME = preview
• DEPLOYMENT_ID = dpl_5fxyip1PaNvgoTF67SUnaMPyZFnv
• ENVIRONMENT_URL = https://webfrontend-fz9zq89zm-acme.vercel.app