Introduction to Checkly
Checkly unites E2E testing and monitoring in one monitoring as code (MaC) workflow, enabled by the Checkly CLI. Monitoring as code is a methodology for managing your monitoring infrastructure using code. It consists of three key steps:
- Code — Define your monitoring setup as code, so you can version, automate and scale them with ease.
- Test — Run your monitors as E2E tests against production and staging from your CI pipeline.
- Deploy — Deploy and lifecycle your monitoring alongside your application deployments.
With MaC, your synthetic monitoring is now programmable, testable, reviewable and works with your dev pipeline. From your IDE, via PR to CI.
Get started with monitoring as code
Get started with monitoring as code by picking the right integration for your team. We recommend using the Checkly CLI for the full code, test and deploy workflow.
Manage and scale your complete monitoring configuration right from your code base with our official Hashicorp Terraform provider.
Get started using the web UI
Not quite ready to start your monitoring as code journey? No problem. Get started using just the web UI and you’ll be monitoring in minutes.
Create a browser check
Use TS / JS with @playwright/test and Headless browsers to navigate, screenshot and assert your key webapp flows.
Create an API check
Monitor the latency and assert the correctness of your API endpoints. Use inline scripts and code to customize everything.
Create a multistep API check
Write Node.js scripts that run multiple API requests in sequence, with arbitrary code between requests and get all the data.
Create a heartbeat check
Monitor your backup jobs, data imports, and other recurring jobs or scripts by pinging Checkly at a regular interval.
Set up alert channels
Get notified about outages, broken transactions or slow downs in your webapps and APIs. Connect to one of our many integrations like Slack, Pagerduty and Discord.
Whip up a status page on your own domain or create an internal dashboard.
Run your Checks wherever you want: inside your firewall, VPC or K8S cluster.
Organize your checks and D.R.Y. up your code and configuration.
You can contribute to this documentation by editing this page on Github