💡 For general support requests and bug reports, please go to <a href="https://checklyhq.com/support">checklyhq.com/support</a>
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 <a href="https://github.com/checkly/public-roadmap/issues/207">https://github.com/checkly/public-roadmap/issues/207</a>

In Review

Scheduling

Increase Response time limit for checks

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

Auth / Access / Roles

Automated Account Creation

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.

General

Store tokens and other credentials across check runs

💡 For general support requests and bug reports, please go to <a href="https://checklyhq.com/support">checklyhq.com/support</a>
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 <a href="https://github.com/checkly/public-roadmap/issues/224">https://github.com/checkly/public-roadmap/issues/224</a>

Alerting

Alerting based on p99 response time

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.
<img src="https://user-images.githubusercontent.com/233663/231202305-4ae356b8-26d8-4c81-aa6a-d1c97572b138.png" alt="image" />
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
<img src="https://user-images.githubusercontent.com/233663/231202514-e81739c7-a243-40e1-853b-55ebad92a358.png" alt="image" />
Additional context
potentially part of #242 and #240 and #65
original GH issue link <a href="https://github.com/checkly/public-roadmap/issues/302">https://github.com/checkly/public-roadmap/issues/302</a>

Status Pages

Show planned maintenance windows in dashboard

One of our checks was failing intermittently when running from one location, so it was not flagged under failures. We only came across these failed runs when looking into the monitoring results of that particular check. <img src="https://fb-usercontent.fra1.cdn.digitaloceanspaces.com/1695816229542.png">Based on the above monitoring results, we see a clear degradation as whenever the check runs from a particular location first, it fails. It would be great if such failed runs are flagged as degradation of the test as, currently, there is no way for us to be aware of the situation unless we drill into the monitoring results.

Failed runs classified as & reported as degradations

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.

Scheduled checks at specific times

Currently it is possible to do the following: <pre><code>npx checkly test someSpecName</code></pre> This is great, but it is currently not possible to deploy/destroy individual checks / check groups without juggling multiple configs. For teams that have multiple check groups in a given repo or have an individual check they want to update on the fly this is currently not possible without potentially overwriting and destroying unrelated checks.

CLI: Ability to deploy/destroy individual checks and check groups

💡 For general support requests and bug reports, please go to <a href="https://checklyhq.com/support">checklyhq.com/support</a>
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 <a href="https://github.com/checkly/public-roadmap/issues/79">https://github.com/checkly/public-roadmap/issues/79</a>

Check Types

Access to the complete Lighthouse metrics

Is your feature request related to a problem? Please describe.
<ol>
<li>I want to allow users to subscribe to status updates from our service.</li>
<li>I want to subscribe to Checkly's status so I know when the service is down or degraded, because:</li>
<li>This might impact how our customers see the status or our service;</li>
<li>We want to know that our services might not be monitored for the duration of the inciden.</li>
</ol>
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 <a href="https://www.githubstatus.com/#">Github's status page</a>:
<img width="418" alt="image" src="https://user-images.githubusercontent.com/2132564/235011867-a4d2119d-df2d-491d-81e3-20fbd0e45f42.png">
Which is similar to <a href="https://status.sentry.io/">Sentry's</a> - 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 <a href="https://github.com/checkly/public-roadmap/issues/304">https://github.com/checkly/public-roadmap/issues/304</a>

Subscribe to status updates

💡 For general support requests and bug reports, please go to <a href="https://checklyhq.com/support">checklyhq.com/support</a>
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 <a href="https://github.com/checkly/public-roadmap/issues/124">https://github.com/checkly/public-roadmap/issues/124</a>

Planned

Dark. Mode.

💡 For general support requests and bug reports, please go to <a href="https://checklyhq.com/support">checklyhq.com/support</a>
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 <a href="https://github.com/checkly/public-roadmap/issues/96">https://github.com/checkly/public-roadmap/issues/96</a>

add ability for tcp and icmp checks.

<h1 id="problem">Problem</h1>
Checkly currently runs your checks in a round-robin fashion, cycling through the locations you have selected for your checks. This is an "easy to reason about" system. 
However, for global infrastructure and apps like CDNs, Anycast-type systems, or any app that resolves one domain to region specific endpoint this is not great as a failing check that fails in one specific region, will resolve if the next region is healthy. The result is that the check does not indicate of one specific region is having problems, whereas others are fine.
<h1 id="proposedsolution">Proposed Solution</h1>
<ul>
<li>Checkly should have the option to schedule checks parallel for all regions, instead of round-robin.</li>
<li>The status of a check should be able to have a "partial" or "regional" outage.</li>
<li>Checkly should be able to alert on regional outages
original GH issue link <a href="https://github.com/checkly/public-roadmap/issues/198">https://github.com/checkly/public-roadmap/issues/198</a></li>
</ul>

Parallel Check Runs

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 <a href="https://github.com/checkly/public-roadmap/issues/46">https://github.com/checkly/public-roadmap/issues/46</a>

In Progress

API Checks

Multi-step API check

💡 For general support requests and bug reports, please go to <a target="_blank" rel="noopener noreferrer nofollow" class="text-indigo-500 dark:text-indigo-300 cursor-pointer text-indigo-500 dark:text-indigo-300 cursor-pointer" href="https://checklyhq.com/support">checklyhq.com/support</a>Is your feature request related to a problem? Please describe.<ul><li>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.</li></ul>Documentation suggesting whitelisting AWS-IPs doesn't make sense, this basically means opening to internet.Describe the solution you'd like<ul><li>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.</li><li>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.</li><li>Having private-link or VPC peer to our VPC. This can help to have checks on private network itself.original GH issue link <a target="_blank" rel="noopener noreferrer nofollow" class="text-indigo-500 dark:text-indigo-300 cursor-pointer text-indigo-500 dark:text-indigo-300 cursor-pointer" href="https://github.com/checkly/public-roadmap/issues/154">https://github.com/checkly/public-roadmap/issues/154</a></li></ul>

Static IPs

Is your feature request related to a problem? Please describe. I have a particular use case for toHaveScreenshot in that my Checkly tests goes through our UI to generate a PDF export of a particular page that you're on. I'd love to be able to compare a screenshot of the PDF generated to a snapshot, as it's impossible to run typical assertions on the information shown in PDFs.Describe the solution you'd like I understand that Checkly agents run in an isolated environment for each test. However, toHaveScreenshot could be supported in a way similar to Buildkite in how it allows you to manage artifacts between builds and build steps, it would be cool if the Checkly agent could detect snapshots generated from toHaveScreenshot, store them somewhere, and then pull them down for the next test to verify against. This could be automatic, or something that the test does, wherer you test can import some kind of Checkly npm package that exports some functions to do these particular tasks.Describe alternatives you've considered What I'm trying to achieve here I can write this code myself. I.e i can store the screenshot snapshots in S3 at the end of my test and write them to disk when the test starts again but that's not ideal at scale if I need to do this in multiple tests. There are visual comparison libraries out there but they aren't in the Checkly runtimes. Adding some kind of visual comparison npm package to the runtimes would suffice too!!!original GH issue link <a target="_blank" rel="noopener noreferrer nofollow" class="text-indigo-500 dark:text-indigo-300 cursor-pointer text-indigo-500 dark:text-indigo-300 cursor-pointer" href="https://github.com/checkly/public-roadmap/issues/282">https://github.com/checkly/public-roadmap/issues/282</a>

Support for `toHaveScreenshot` / visual regression testing

We want to enable better integration with 3rd party dashboard tooling, APM integrators and other by providing more data points on the Checkly Prometheus exporter. Prime candidates are: <ul><li>connection phase metrics for API checks, e.g. TTFB, dns</li><li>more metrics for browser checks like web vitals, TTFB etc.</li></ul>

Integrations

Extend Prometheus exporter with extra / more data points

The current retry strategy for all checks is fairly limited. We want to expand the possibilities for retrying with two options: - same region: right now, retries are always scheduled on a different region than the original attempt. This is not ideal for geo-fenced checks or region-aware websites rendering different content for different regions. - backoff strategies: we want to enable multiple retries according to a strategy the user can define: linear or exponential so the target system has more time to recover from an initial failure.

Completed

Smarter retries strategies: same region and backoff

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 <a href="https://github.com/checkly/public-roadmap/issues/23">https://github.com/checkly/public-roadmap/issues/23</a>

Private Dashboards

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
<ul>
<li>http://healthchecks.io/ (open source self-hosted version available)</li>
<li>https://deadmanssnitch.com/ </li>
<li>https://docs.opsgenie.com/docs/heartbeat-monitoring </li>
</ul>
Additional context
original GH issue link <a href="https://github.com/checkly/public-roadmap/issues/72">https://github.com/checkly/public-roadmap/issues/72</a>

Deadmans Switch type checks

Would like an option to further simplify a dashboard to not show the response time, but just a red or green light.

Simple Dashboard

Describe the solution you'd like
Checkly's existing alert channels cover almost all the mediums from which I need alerts, except for something that will ring persistently and wake me from sleep — a phone call. :)
Describe alternatives you've considered
There are more comprehensive solutions that presumably include phone call alerts, as part of their broader suites of functionality -- PagerDuty, OpsGenie, Spike, etc. I'm working on cobbling this together via Checkly webhooks and the Twilio API -- https://www.twilio.com/docs/studio/rest-api/v2/execution -- but it'd be nice if this were as simple as configuring your other channels. 
Additional context
I'm not looking for comprehensive stuff like scheduling, multiple phone number support, etc. Just a simple phone call to a single number if there's an outage.
Thanks for considering!
original GH issue link <a href="https://github.com/checkly/public-roadmap/issues/199">https://github.com/checkly/public-roadmap/issues/199</a>

Alert channel for Phone calls

Is your feature request related to a problem? Please describe.
Checkly agent is great but it is a lot of manual work to get it up and running in my Kubernetes cluster. I need to understand the <a href="https://www.checklyhq.com/docs/private-locations/checkly-agent-guide/">documentation</a> and then translate this into a Deployment spec and run it in my cluster.
Describe the solution you'd like
I'd like to have a Helm chart, where a new installation would be only three steps:
<pre><code>helm repo add checkly https://charts.checklyhq.com
helm repo update
helm upgrade --install checkly-agent checkly/checkly-agent \
 --set config.api_key='YOUR.AGENT.API.KEY'
</code></pre>
or to update to a new version
<pre><code>helm repo update
helm upgrade checkly-agent checkly/checkly-agent --reuse-values
</code></pre>
All customizations would happen in a Helm style in a separate <code>values.yaml</code>.
Describe alternatives you've considered
Hand roll it by myself in my cluster. Write my own Helm chart. Use other config management tools like Terraform or Ansible to write the deployment.
original GH issue link <a href="https://github.com/checkly/public-roadmap/issues/285">https://github.com/checkly/public-roadmap/issues/285</a>

Checkly Agent

Provide a Helm chart for Checkly Agent

By default, a maintenance window has no checks applied. The text explaining this was overlooked by one of our team resulting in a maintenance period that had no effect. Can we either prevent saving a maintenance period with no checks, or show a very loud warning on that page?

Maintenance Windows

Handling a maintenance period with no checks

<h1>Problem</h1>It's now not possible to attribute who created a check, snippet or any other entity in Checkly and who edited it afterwards.<h1>Solution</h1><ul><li>track creator and editors for all entities in Checkly</li><li>show user avatars on the UI (similar to GitHub or any other SaaS product showing creators and editors</li><li>show origin of the resource, e.g. whether it was created via the CLI, WEB UI, Terraform or Pulumi.</li><li>original GH issue link <a target="_blank" rel="noopener noreferrer nofollow" class="text-indigo-500 dark:text-indigo-300 cursor-pointer text-indigo-500 dark:text-indigo-300 cursor-pointer text-indigo-500 dark:text-indigo-300 cursor-pointer text-indigo-500 dark:text-indigo-300 cursor-pointer" href="https://github.com/checkly/public-roadmap/issues/202">https://github.com/checkly/public-roadmap/issues/202</a></li></ul>

User activity metadata in UI and DB

Bonjour, j'ai beaucoup de mal avec l'anglais, de nos jours, les applications multi langages ne sont pas très compliquées à mettre en place, je pense que ce serait un gros plus pour votre application.Personnellement, c'est ce qui me bloque pour l'acquisition de votre produit. Cordialement, Michel Poulet. Société des auteurs et compositeurs de musiqueNeuilly sur seine, France.

Interface Language ...

The <a target="_blank" rel="noopener noreferrer nofollow" class="text-indigo-500 dark:text-indigo-300 cursor-pointer" href="https://create.t3.gg">t3 stack</a> is a very popular tool among the typescript community. It comes with validated env support. We got a env.e2e.ts file for our playwright tests and we busy setting up checkly, but right now it means we cant use this validated env file and need to switch to process.env.* the old fashioned way. If you could support those 2 packages at runtime, that would be fantastic! See our env.e2e.ts file below<pre><code class="language-ts">/* eslint-disable @typescript-eslint/no-var-requires */
import { createEnv } from '@t3-oss/env-nextjs'
import { z } from 'zod'

// This is needed in test environment, but not nextjs
require('dotenv').config()

export const env = createEnv({
 /**
 * Specify your playwright environment variables schema here.
 */
 server: {
 NODE_ENV: z.enum(['test']),
 BASE_URL: z.string().url().default('http://localhost:3000'),
 TEST_USER_EMAIL: z.string().email(),
 TEST_USER_PASSWORD: z.string().min(8),
 CI: z
 .string()
 .optional()
 .transform((value) =&gt; value === 'true'),
 },

 runtimeEnv: process.env as Record&lt;string, string | boolean&gt;,

 onInvalidAccess: (variable) =&gt; {
 throw new Error(`Invalid access of env variable: ${variable}`)
 },
})
</code></pre>

Runtimes

Support @t3-oss/env-nextjs and zod in runtime

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:<ul><li>Common viewport for tests</li><li>Common setup, teardown for tests</li><li>Common storageState for tests</li><li>Turn screenshot, trace, video on/off</li><li>And all the other useful playwright.config features that make playwright awesome</li></ul>