# Checkly guides - Checkly Docs

> Hands-on guides that take you from a first Checkly project to monitoring that detects failures, tells the right people, and helps you fix them.

Source: https://www.checklyhq.com/docs/guides/overview/

---

Getting Started

# Checkly guides

Hands-on guides that take you from a first Checkly project to monitoring that detects failures, tells the right people, and helps you fix them.

Each guide does one real job from start to finish, with a sample project you can clone and a prompt you can hand to your coding agent. If you haven’t set up a project yet, start with the [quickstart](https://www.checklyhq.com/docs/quickstart), then work through the guides in order or jump to the one you need.

## ​ Getting started

## Structure a project

Organize checks by service with groups, keep shared settings in one config, and deploy from CI on every merge

## Turn Playwright tests into monitors

Run the Playwright tests you already have as scheduled production monitors, without rewriting them

## ​ Detect

## Cover every endpoint

Turn a list of pages into URL monitors, tell slow from down, and watch the certificate under all of them

## Monitor your API end to end

Assert on status, headers, and body for every endpoint, tell slow from down, and authenticate with setup and teardown scripts

## Monitor the content customers see

Assert that the text that sells is on the page, in the right place, exactly once, and that error copy never is

## Monitor from around the globe

Run checks from where your users are, in parallel, and let the regions vote before you get paged

## Run checks on every deploy

Test pull request previews before merging and validate production deployments after they ship

## Setup and teardown scripts

Create test data before an API check runs, clean it up afterward, and scrub sensitive values from results

## Control monitoring with agents

Create, configure, and update your monitoring through prompts to your coding agent

## Checkly and Claude Code

Set up Claude Code to generate and deploy URL monitors and browser checks for your services

## ​ Communicate

## Alert without the noise

Route alerts by urgency, retry blips in place, escalate on consecutive runs, and mute planned deploys

## Status pages backed by monitors

Build a status page in code whose incidents open and resolve from the checks that test each feature

## ​ Resolve

## Debug a failed check

Go from a failing check to its root cause with the CLI, the Playwright trace, and Rocky AI, then confirm the fix

## ​ Examples

## Monitor a checkout flow

Browse, search, add to cart, and checkout as one Playwright Check Suite with safe test data

## Monitor a shop with Terraform

Declare the alert channel, group, browser checks, and API check for a shop in Terraform

## Monitor the Stripe API

Check a third-party API your product depends on with API check assertions and response time limits

## Monitor an OpenAPI spec

Generate API checks from an OpenAPI or Swagger specification

Was this page helpful?

[Suggest edits](https://github.com/checkly/docs/edit/main/guides/overview.mdx)[Raise issue](https://github.com/checkly/docs/issues/new?title=Issue%20on%20docs&body=Path:%20/guides/overview)

[Structure a Checkly project for a real codebase Next](https://www.checklyhq.com/docs/guides/structuring-a-checkly-project)

[x](https://x.com/checklyhq)[github](https://github.com/checkly)[linkedin](https://linkedin.com/company/checkly)

[Powered by This documentation is built and hosted on Mintlify, a developer documentation platform](https://www.mintlify.com/?utm_campaign=poweredBy&utm_medium=referral&utm_source=checkly-422f444a)