2
Access to the complete Lighthouse metrics
π‘ For general support requests and bug reports, please go to checklyhq.com/support Is your feature request related to a problem? Please describe. We are not able to access Lighthouse report details from the API when executing browser checks. Describe the solution you'd like We would like to be able to access Lighthouse report details so we can fail tests when performance degrades. Describe alternatives you've considered Some data is available thru the performance.getEntriesByName object, we are using this as a workaround. original GH issue link https://github.com/checkly/public-roadmap/issues/79
π‘ Feature Request
In Review
Check Types
Absolute duration of downtimes
At the moment there is only a percentage about a down time. I'd like to see the absolute duration of a downtime. original GH issue link https://github.com/checkly/public-roadmap/issues/280
Alerting
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
Status Pages
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
Planned
API Checks
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
1
Private Dashboards
As a Checkly administrator I would like to create private dashboards (View only TV mode style) and share them with third parties using individual username/password or other secure methods that ensure the dashboards are only viewable by authorised users. These users should not count towards the "employee or user" count for billing but may be bundled as part of billing packages. original GH issue link https://github.com/checkly/public-roadmap/issues/23
In Progress
Deadmans Switch type checks
Is your feature request related to a problem? Please describe. Uptime monitoring can be divided into roughly 2 categories Remote Checks This is currently what checkly focuses on and is a simple check that is made from a remote server on a fixed interval and if any of these checks fail notification is sent. Deadmanswitches These are actually the inverse, these are checks that are generated from the client and if any of these fail to report notification is sent. These are insanely valuable for background processing or database backups where you need to verify that the job successfully completed. See https://en.wikipedia.org/wiki/Deadman%27sswitch Describe the solution you'd like I would love deadman switch type check added to checkly so we can consolidate our monitoring offering. Describe alternatives you've considered http://healthchecks.io/ (open source self-hosted version available) https://deadmanssnitch.com/ https://docs.opsgenie.com/docs/heartbeat-monitoring Additional context original GH issue link https://github.com/checkly/public-roadmap/issues/72
Support GraphQL Variables
Is your feature request related to a problem? Please describe. We're building a GraphQL Endpoint. Checkly allows using GraphQL Queries in API Tests. https://www.checklyhq.com/docs/api-checks/request-settings/ But in Checkly's UI, can't using GraphQL Variables. Describe the solution you'd like Add a form to write GraphQL Variables. Describe alternatives you've considered Using JSON body type as a workaround. But, this is painful for me. original GH issue link https://github.com/checkly/public-roadmap/issues/73
Support JSON schema
Is your feature request related to a problem? Please describe. Our company uses "Design-first approach" regarding APIs so we always define OpenAPI spec before doing any coding. Because of that we are maximising benefits from having this spec, like validating data in servers, generating clients etc⦠You already have basic support for OpenAPI specs, but you only use routes. You don't use schema in any way. Describe the solution you'd like When importing OpenAPI spec, not only generate test routes, but also generate JSON schema that will be used to do assertions without any user input. Describe alternatives you've considered At least allow to define general data types for assertions :) So I could easily define "this field should be string with min-length of 2 characters" or "this should be floating point number" instead of giving exact value. original GH issue link https://github.com/checkly/public-roadmap/issues/75
add ability for tcp and icmp 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
Tell Checkly how they could make the product more useful to you.