Open paulb-elastic opened 3 years ago
Pinging @elastic/uptime (Team:Uptime)
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This is still on our backlog to do and will still be a useful feature (cert checks is a well used feature in the lightweight checks)
Hi! We just realized that we haven't looked into this issue in a while. We're sorry!
We're labeling this issue as Stale
to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1
.
Thank you for your contribution!
:+1:
Existing TLS certificate checks for Heartbeat monitors are useful to give an early warning that certificates are going to expire (and give users the time to renew them before they expire which may well impact the availability of the site).
These are not currently available for browser based Synthetics monitors, but the requirement and value that certificate checks provides, is just as valuable for these monitors (arguably more so as more hosts and content are included in Synthetic monitors, with a wider number of hosts needed to deliver it to make up the website).
Use case
This is an enhancement to the initial root URL host certificates check covered in this issue.
Feature:
Design: as well as the list of certificates and their status (on the main Certificates status page, we may want to consider an enhanced visualisation of this, such that expiring hosts could be identified more easily, for example on the waterfall chart). This should be addressed with a separate design ticket for Uptime.