Code-First Monitoring With the Checkly CLI

The Checkly CLI empowers you with a Monitoring as Code (MaC) workflow that allows you to code your monitors and maintain them version-controlled. Adopt shift-left monitoring that supports your modern DevOps culture. Compatible with Playwright and Terraform.

Start for free Read docs

new BrowserCheck('homepage-browser-check-1', {
  name: 'Browser Check #1',
  frequency: 10,
  regions: ['us-east-1', 'eu-west-1'],
  code: {
    entrypoint: './home.spec.js'
  }
})

new ApiCheck('product-api-check-1', {
  name: 'Product API - fetch products',
  degradedResponseTime: 10000,
  maxResponseTime: 20000,
  requests: {
    url: "https://api.acme.com/v1/products",
    method: "GET",
    assertions: [AssertionBuilder.statusCode().equals(200)]
  }
})

Trusted By Engineering Teams At

Your App’s Code Lives in Source Control. Your Monitoring Should, Too

Integrating the Checkly CLI in your CI/CD from pre-prod and production ensures the reliability and availability of your apps and services at scale.

Add to cart

Purchase

API

Alert

Code-first workflow

Your entire monitoring workflow, defined as code in your existing code base.

Monitor your APIs

Seamlessly integrate API monitoring into your E2E testing and monitoring regimen.

Harness the Power of Playwright

Fully harness the power of Playwright to validate the reliability of your web app with Checkly’s browser checks.

Run From Your Repository

Store all monitoring resources in your Git repo, alongside your application code: just like the unit testing patterns you are familiar with.

Typescript First

Code, compose, and structure your monitoring resources using TypeScript. No YAML-engineering needed.

Code and Collaborate

Use any CI platform to collaborate with your team to code, test, and deploy E2E browser and API checks.

Code all your resources

Your app’s code lives in your repository. Your monitoring should too. Create resources in a programmable way: use loops, read files or add conditions. You code your monitoring infrastructure instead of configuring it.

new BrowserCheck('homepage-browser-check-1', {
  name: 'Browser Check #1',
  frequency: 10,
  regions: ['us-east-1', 'eu-west-1'],
  code: {
    entrypoint: './home.spec.js'
  }
})

new ApiCheck('product-api-check-1', {
  name: 'Product API - fetch products',
  degradedResponseTime: 10000,
  maxResponseTime: 20000,
  requests: {
    url: "https://api.acme.com/v1/products",
    method: "GET",
    assertions: [AssertionBuilder.statusCode().equals(200)]
  }
})

Test locally and in CI/CD

Test your future monitoring resources from your local machine or during CI deployments—all running on Checkly’s global infrastructure.

$ npx checkly test

Running 2 checks in eu-west-1.

src/api/__checks__/product-api.check.ts
   ✔ Product API - fetch products (65ms)

src/__checks__/homepage.check.ts
   ✔ Homepage (7s)

2 passed, 2 total

Deploy with confidence

Deploy, lifecycle, and scale your end-to-end testing and monitoring solution from the command line alongside your application deployments.

$ npx checkly deploy --preview

Create: 
    BrowserCheck: homepage-browser-check-1
    ApiCheck: product-api-check-1

$ npx checkly deploy

? You are about to deploy your project "Monitoring as code" to account "Production". 
Do you want to continue? Yes

Successfully deployed project "Monitoring as code" to account "Production".