Arnaud Lapiere
My feedback
5 results found
-
109 votes
Before this is implemented we can recommend some alternative services:
- https://healthchecks.io (SaaS or open source: https://github.com/healthchecks/healthchecks)
- https://deadmanssnitch.com
- https://cronitor.ioAn error occurred while saving the comment -
8 votes
Hello,
Actually 14, 7, 1 is already the special schedule for let’s encrypt certificates. This is automatically detected by updown.io so you don’t have to, normal 1-year certificates get an additional 30 days reminder.
The threshold for let’s encrypt certs starts at 14 days because the default renew delay is 30 days before expiration: https://certbot.eff.org/docs/using.html. This can be down to 23 days with a weekly cron for example (pretty common) so that’s why we chose 14 days, so you have plenty of time to renew but still have time to investigate and fix any potential auto-renew issues.
If you’d rather renew your cert only 5 days before expiration that’s up to you but we won’t recommend or support this configuration as we consider it dangerous ☺
I’ll mark this suggestion as “Under Review” to measure the need for this.
Arnaud Lapiere
shared this idea
·
-
83 votes
There's no plan to add a new feature for this, but it's already possible to do basic grouping by using the check alias (e.g. "Client A / Site 1"), this way you can sort by Alias in your dashboard and have your checks grouped by client/project/etc.
An error occurred while saving the comment Arnaud Lapiere
commented
Additional use case (Am I the only one doing this ? ) I have several probes for important websites, with text string check, so I can make sure there is no regression .
(It already happened to me I had the homepage working, but no others, due to Wordpress permalinks issue) --> grouping probes of the same website in a group/tag make sense, of course -
8 votesArnaud Lapiere
supported this idea
·
-
4 votesArnaud Lapiere
supported this idea
·
https://github.com/healthchecks/healthchecks is open source, as a good starting point