Here’s a roundup of the new features and improvements we shipped over the past month.

DNS monitors are here!

We’re excited to share that DNS monitors are now available on all plans.

DNS monitors help you track DNS resolution and lookup times, so you can spot misconfigurations, expired records, or resolver latency issues before your customers notice.

Learn more:

• Check out the change log update.

• Jump into the developer docs.

• Or try it out right away!

Error Groups for Test Sessions

You can now find all errors that happened during Test Sessions in the new “Error Groups” tab. Error Groups for Test Sessions work the same way as Error Groups for scheduled checks and monitors, but add dimensions for "project" and "environment" properties, populated by the Checkly CLI.

• This feature is now live for all users on all plans at no extra charge.

• Test Session Error Groups are in early development; expect updates in the coming days and weeks.

• If you are running the Checkly Agent on Private Locations, make sure you’re on version 6.1.5 or later. Check how to upgrade here.

Checkly and Playwright

Our latest flagship checks, Playwright Check Suites, now come with new features. Additionally, there's a new Playwright Reporter, which you can enable by adding it to your playwright.config.ts and running npx playwright test.

Playwright Check Suites

• There’s a new graph on the Check Overview page for your Playwright Check Suite. It gives you a clear breakdown of individual test case statuses.

  

• Terraform support for Playwright Check Suites starting in version v1.17.0.

• Private Locations now support playwright test performance, availability metrics and graphs. Starting on v6.1.5.

• Support for a new CHECKLY environment variable that lets you define specific behaviour when running scheduled Playwright Check Suites. Check the documentation here.

  • By default, when running npx checkly test, npx checkly trigger or npx checkly pw-test, the variable CI=1 is set, since you’re running your tests.

  • When using scheduled checks, CI will be unset since they’re running against production.

  • To use custom test retries, traces or workers values when running your Playwright Check Suite on a schedule, you can now use the variable CHECKLY in your playwright.config.ts, which is set to 1 for scheduled Checkly runs. Use

    CHECKLY_RUN_SOURCE for advanced configuration that depends on all the different Checkly run types.

Playwright Reporter (Beta)

Checkly’s Playwright Reporter is here to make it easier to keep track of your Playwright tests wherever they run: locally, in CI/CD, or as monitors in Playwright Check Suites. It’s still early, we’ve built it to bring more clarity to your test suite:

• Central view of all Playwright test runs across environments.

• Clearer insight into flaky, slow, and failing tests.

• Helpful debugging assets (videos, traces, snapshots).

Developer Experience

• Checkly import is now live in the UI: The old code snippets shown in the “export to code” modal have been removed and replaced with CLI import instructions. This makes it easy to pull UI-created resources into your codebase, where they can be fully version-controlled and automated through CI/CD. Learn more in our guide on Monitoring as Code.

Fixes

• Check tags in PagerDuty alert payloads: Tags from a failing check are now included in the payload sent to PagerDuty.

• API docs cleanup: We’ve fixed various inconsistencies (e.g. authorization header info) and added missing examples (e.g. on retrieving account IDs). Further restructuring is planned to improve clarity. If you spot other issues in the API docs, please let us know.

• Rate limit visibility: API responses now include rate-limit headers, helping you monitor and manage your API usage.

• Enhanced dark mode: Date picker, error states, and input fields now render more clearly in dark mode.

Got feedback? We’d love to hear from you!

You can share your feedback on our feedback hub or connect via the Checkly community Slack.

Happy monitoring!