In Review
181Under consideration
Scheduled checks at specific times
It would be great to be able to run checks at specific times (like a cron job schedule), as we have an API that publishes certain customer-critical data daily at specific times. So instead of every X minutes which can be any time depending on when the check is first created, we would be able to run reliably at specific times.
Mark/Delete failures as false-positive
We use Checkly statistics to monitor our uptime %. Sometimes we have failures that are false positives (since there was a bug in the test or specific to the test environment, and not in production, or just things didn't really break). We don't want to count those failures as downtime, hopefully with adding a note to why. Thanks!
Aggregate alerts under a group
Hey Checkly team :wave: Currently if we have multiple checks under a group and alerting is setup to be routed to tools like PagerDuty or OpsGenie, there are times where we'll be bombarded with alerts. This happens when the check dependencies all share the same downstream call, and that downstream call is problematic. If its possible to aggregate the alerts by the group, this would drastically reduce the alerting noise if we get into another instance where all checks under a group starts to fail. I'm not sure if this is possible due to a limitation from OpsGenie, PagerDuty etc. But the end goal would be to send a single alert that references the group, and additional metadata is added which specifies which check is failing, as opposed to each check being an individual alert.
Increase Response time limit for checks
💡 For general support requests and bug reports, please go to checklyhq.com/support Is your feature request related to a problem? Please describe. We have a time out of apis defined at our load balancer level as 60 sec, checkly times out the request at 30 sec max with which we are not able to identify if the system is not responding or checkly servers not able to communicate with our servers. Describe the solution you'd like Providing an option of custom timeout (maximum configurable to 100 sec) Describe alternatives you've considered NA for now Additional context NA original GH issue link https://github.com/checkly/public-roadmap/issues/207
Customization of email alert content
Hello Team, I am requesting a feature of customizing email alert content. Where we can attach image showing failure and url and other required information where test is being run. Regards Anil
Automated Account Creation
HI Checkly Team, We have lots of Checkly accounts created under our org and are looking to get more in the future. We have a tooling suite for creating checks on Checkly and its pretty much streamlined except for the account creation part. We are looking to streamline account creations as well, as the current process is to email our Checkly representative and that has a turn-around time of ~24hours. We are looking to have this automated via API, preferably get it to be a Terraform resource. We are currently using terraform to create Checkly resources, but whatever way would be faster to get this to become a reality would be great
Support for more flexible thresholds in Alerts escalations
Currently, time-based escalation cannot be set to less than 5 minutes. In most cases, this threshold is pretty high for sensitive API checks. I'd highly appreciate it if you could make it more flexible. time_based_escalation { minutes_failing_threshold = 5 // (TIME_BASED escalation only) after how many minutes spent in failing state to send an alert () } As of now, it can be set to 5, 10, 15, 30 minutes The requested thresholds are, 1, 2, 3, 4, 5 minutes Reference: https://www.checklyhq.com/docs/terraform-provider/alerting/#alert-settings
Alerting based on p99 response time
💡 For general support requests and bug reports, please go to checklyhq.com/support Is your feature request related to a problem? Please describe. Instead of alerting on a single request being slow, I'd like to alert if the average or p95 time exceeds a limit. Describe the solution you'd like When setting Assertions, I would like to be able to chose "average response time" or "p95 response time" as the Property value for a Response Time check. Describe alternatives you've considered Checking the dashboard manually? I'm not sure what other options there are. Additional context A single slow request may not be worth an alert. But several slow requests will raise our average/p95 response times and are worth investigating. original GH issue link https://github.com/checkly/public-roadmap/issues/224
Record the state of the last known good
When a test fails it would be handy to see what the last known good looked like. If a test fails we can see a video, screenshots, and trace which helps with working out why it's failing. Sometimes it will be handy to view the video of the last known good test run. E.g we get an alert advising the text has changed, looking at a video of the test load when it was green will show the text before it was removed. This could give you some useful information when tracking down the cause. I appreciate that you cant keep all the data for green runs as that would need a load of storage, but you could configure it to keep data of just the last good test run before a failure.
Mute/disable checks for x amout of time
User story As a maintainer of our checkly checks I want to be able to disable or mute checks for x amount of time so I don't forget to reenable them after fixing a check. Problem Description When a check fails it might be because some kind of bug that needs to be fixed in the check itself or the application that's being monitored. This can take time, usually I mute the check until I am finished and reenable them afterwards. It has happened that I forgot to reenable them for a few days which is unwanted. Proposed solution When I mute or deactivate the check I'd like the option to choose a date and time on which it should be reenabled again. It'd be nice to have a few "quick" options like: 1 hour 6 hours 1 day 1 week infinite And to have the option to select any date in the future.
Planned
1Committed and queued
Next
1Committed and queued
In Progress
1Actively being built
Completed
110Recently shipped
Global playwright.config.ts support (viewport, setup, teardown, storageState ...)
To truly unite E2E testing and monitoring, Checkly CLI has to support the global configuration defined in playwright.config.ts, so that it can be used in both scenarios. playwright.config.ts is very useful to handle stuff like: Common viewport for tests Common setup, teardown for tests Common storageState for tests Turn screenshot, trace, video on/off And all the other useful playwright.config features that make playwright awesome
Dark. Mode.
💡 For general support requests and bug reports, please go to checklyhq.com/support Is your feature request related to a problem? Please describe. My eyes at night. It hurz Describe the solution you'd like Dark mode. Describe alternatives you've considered Wearing sunglasses looking at Checkly, at night. Additional context 🌚 original GH issue link https://github.com/checkly/public-roadmap/issues/124
Subscribe to status updates
Is your feature request related to a problem? Please describe. I want to allow users to subscribe to status updates from our service. I want to subscribe to Checkly's status so I know when the service is down or degraded, because: This might impact how our customers see the status or our service; We want to know that our services might not be monitored for the duration of the inciden. Describe the solution you'd like An option on Checkly's status page allowing users to subscribe to updates. Ideally, they would be able to choose between multiple ways to get notifications, like RSS/Atom feeds, email, Slack, maybe even webhook - see example from Github's status page: Which is similar to Sentry's - it seems they use Atlassian Status Page. I see #297 asks for a specific type of update, but I'd like to have more options than just email. original GH issue link https://github.com/checkly/public-roadmap/issues/304
Multi-step API check
Describe the solution you'd like For a CRUD API set, it makes sense to test these in a multi-step sequence. For example, to do a POST to create an object, assert that it was created in the response, then POST to delete the object and assert the response. Describe alternatives you've considered Could potentially do this in setup/teardown scripts, although then it is less clear in the monitoring. original GH issue link https://github.com/checkly/public-roadmap/issues/46
DNS checks
I want to check the core metrics and correctness of my DNS and DNS records. A DNS check should be able to: monitor the response time of a DNS query. assert the corrects values and existence of specific DNS records.
Static IPs
💡 For general support requests and bug reports, please go to checklyhq.com/support Is your feature request related to a problem? Please describe. I would like to browser-checks for our internal tools (Blocked IPs, Some in private network). Which is not open public? I don't have much control on web server level to these tools. Currently, there is no way to have checks to these. Documentation suggesting whitelisting AWS-IPs doesn't make sense, this basically means opening to internet. Describe the solution you'd like Static IP sets. I don't know how your infrastructure looks like, if it's possible to run check runners behind few NATs. We can have IPs sets which can be whitelisted in our LB/firewalls. Any ways these IPs can be changed if your infra needs some update, So an API endpoint which list current IPs help more, to automate IP whitelisting. If NAT is not a possible solution, having an open AWS SNS, Even-Bridge some sort where I can subscribe in our AWS accounts to load new IPs to SGs using lambda. Having private-link or VPC peer to our VPC. This can help to have checks on private network itself. original GH issue link https://github.com/checkly/public-roadmap/issues/154
Customisation of NPM Dependencies
Summary: Allow users to customise or override the NPM dependencies within the Checkly runtime environment. Description: Currently, users are restricted to a set list of packages and versions in the Checkly runtime, which may not cover all the specific use cases or compatibility issues they encounter. As a Checkly user, I need to be able to dynamically use packages in my own runtime. I process dependency updates in projects regularly to use the latest versions for new features and security updates.
Store tokens and other credentials across check runs
Any check that requires auth / credentials that expire needs to fetch these credentials on every check run. While this is the safest way to make sure checks are authenticated, it creates friction: - extra runtime in a browser check or setup script. - extra load on any authentication endpoint. - waste of general cloud resource. A user should be able to store tokens securely in a check run and fetch or revalidate the credentials when or before they expire.
add ability for tcp checks.
💡 For general support requests and bug reports, please go to checklyhq.com/support Is your feature request related to a problem? Please describe. We do http monitoring but we have some api's that are not http but are at tcp level. Having monitoring for tcp connections basic check on URL and any Port is great. Can integrate tls as well. Describe the solution you'd like as part of addition of api checks, we can add tcp as an option in the drop down. Describe alternatives you've considered using datadog right now . Additional context Add any other context or screenshots about the feature request here. original GH issue link https://github.com/checkly/public-roadmap/issues/96
Show planned maintenance windows in dashboard
Is your feature request related to a problem? Please describe. we're very happy with the new dashboards, which have become integral to our communication (https://status.qfield.cloud/). There is, unfortunately, a big shortcoming for us. A planned maintenance window is only visible once it becomes active. To really become fully operational as a status page, these should be visible ahead of time. Describe the solution you'd like show planned maintenance as non-active planned incidents Describe alternatives you've considered A minimal solution could be to show planned maintenance as in the admin dashboard Additional context potentially part of #242 and #240 and #65 original GH issue link https://github.com/checkly/public-roadmap/issues/302