February 4th, 2025
New
We’ve been building some exciting features over January that we’d like to share with you all.
TCP Checks are now available in Open Beta for all plans!
Use TCP checks to monitor infrastructure components. Simply specify your hostname or IP address and the TCP port to target:
Learn more in the TCP checks documentation.
Delivering joyful developer experiences with Checkly is at the heart of what we do! This January, we’ve rolled out powerful enhancements to the Checkly CLI and API— designed to improve your workflow and make development smoother at every step 🚀
🕵🏻 You can now filter for check results with failures when querying /v2/check-results
with the boolean parameter hasFailures
— it’ll be true
when the result has one or more failures. Check out GET v2/check-results
documentation.
🚨 We’ve increased the number of alert channels that support custom handling of the check result error message. Use the variable $CHECK_ERROR_MESSAGE
in these additional alert channels: Incident.io, Firehydrant, Discord, GitLab, Splunk, Teams, Telegram, Colarogix, and custom webhooks. Learn all about using variables in alerts here.
🌐 It’s now possible to set a Proxy URL for Private Locations through the Checkly API, matching the API functionality with the UI. ▶️ Create a Private location using the API .
</>
Improving code imports!🛣️ Support for TypeScript config paths
is now here to simplify your import(s).
↪️ We’ve also added support for import 'node:path'
. (Previously only import 'path'
worked.)
↪️ You can also now use import './file.js'
and have it map to ./file.ts
.
🔠 Checks in the Home dashboard are now ordered alphabetically — also checks inside Check groups and groups themselves! — making it easier for you to find the check that you’re looking for.
🕸️ Revamped our log-in and sign-up pages; it’ll now be smoother for those of you using SSO!
🔢 Improved the UI for setting response time limits on checks – The dropdown has been replaced with a numeric input field, so you can set limits with more flexibility.
Fixed the status displayed in the UI when a check is being retried. Once a check has failed, it now displays the status as failed until it succeeds.
Fixed a UI bug unfolding Test Steps in a test case when there were several test cases in a single check result.
Environment variables now ignore casing when checking if there are duplicate ones, so you can’t create both Hello
and hello
as distinct environment variables from now on.
We build Checkly with you in mind! And your feedback shapes our roadmap; tell us what you think and what you’d love to see next! Leave a note in the feedback hub or connect with us in the Checkly community Slack.