Monitoring reinvented for engineering teams

Monitoring as Code (MaC) enables application, site reliability, and quality engineers to create, configure, and collaborate over their entire reliability workflow straight from their IDE.

Install the CLI Book a demo

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

What is Monitoring as Code?

Monitoring as Code transforms monitoring into a repeatable, maintainable, and scalable practice, making it easier to manage complex systems reliably.

Add to cart

Purchase

Payment

Alert

Your entire monitoring workflow, defined as config files along with Playwright code, OpenAPI specifications, or Terraform scripts in your existing code base, can be automatically updated and deployed across test, staging, and production servers.

Scalable

As your system grows and both new services and features are added, monitoring as code allows for programatic updates and changes to keep up with the pace of application changes.

Collaborative

Developers, SRE Teams, and other operational teams can collaborate on monitoring configurations and checks using familiar development tools and practices, which promotes a shared understanding and quicker troubleshooting when an error does occur in production.

Ship with confidence – monitoring as code explained in three minutes.

Checkly CLI

Use our native JavaScript/TypeScript workflow to code, test, and deploy your sites with confidence.

Use the Checkly CLI

Terraform

Write your check definitions as code with our best-in-class Terraform provider for easy creation and maintenance at scale.

Use Terraform

Pulumi

Define your checks as code with our Pulumi provider makes monitoring large websites and APIs a breeze.

Use Pulumi

Public API

Use Checkly's API to tailor your monitoring setup to your project.

Use the API

Build tests, monitors, and configure your alerting workflow in your IDE

Your app’s code lives in your repository. Your monitoring should too. Create resources in a programmable way, coding them instead of configuring them.

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)]
  }
})

Run tests locally or in your CI/CD to make sure everything passes

Run UI and API tests on Checkly during CI/CD to catch bugs and performance errors before changes even hit production.

$ 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 tests as real-time monitors running against your production environment for complete confidence

Once your tests pass and your application is deployed, Checkly runs your tests and uptime monitors at a high-frequency across our global infrastructure to continuously detect errors or performance issues that affect customers in production.

$ 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".