TwiN

Adding support for other duration units just for certificate expiration would create confusion. Beyond that, I'm ok with adding support for days, but weeks, months and years I think is...

The negative values is just what it shows when there's no expiration date found. RDAP support was recently added for the `[DOMAIN_EXPIRATION]` placeholder, so hopefully that'll reduce the number of...

I'm willing to consider making an exception _specifically_ for `www` because it's such a widely used cname, assuming the change is straightforward enough. As for other CNAMEs (e.g. `api.example.com`, `docs.example.com`,...

Ugh, I'm second guessing my previous stance. If `[DOMAIN_EXPIRATION]` resolves to `-9223372036854` AND kind of sort of looks like a subdomain (i.e. has at least 2 dots), then fall back...

This isn't a bad idea, but what if there are multiple reasons for the endpoint being unhealthy? For instance, what if, for the first 20 minutes, it's unhealthy because of...

Perhaps having it as a set (unique values) would be sufficient for now. Just a heads up, the current implementation is missing a lot of bits and pieces, the biggest...

> Perhaps something like this then, where we aggregate the unique failures and show the timestamp of failure? This is a great idea, but there's a few things we'll have...

I'm a little perplexed, because on one hand, this certainly makes it easier for users, but on the other hand, this isn't secure. I'm all for making Gatus easier to...

> To be honest, I don't see any security-related downsides to using secrets in query parameters It's not secure, because at layers from both the ingress and egress level might...

New UI thread: https://github.com/TwiN/gatus/discussions/1195