TwiN

It's not that I'm against the idea, but with the way uptime retention is currently implemented, this would imply having to store 8760 rows per endpoint instead of 240. For...

It's also a matter of performance. There are some users configuring a single Gatus instance with as much as 3500 endpoints - that'd amount to `3500 x 24 x 365...

To implement this, a suitable solution would be to merge all entries older than 48 hours into daily entries which would effectively be the the first unix hour of the...

For now, let's settle for 30 days, like #128 also requested. Once I'm more confident with the implementation I went with, I can look into expending the badge to 1y....

@freshpr Read the comment above yours, it explains it, but to reiterate, I closed this ticket as a duplicate of #128, which was also about increasing badge uptime (albeit 30d...

Good idea. This would just involve making this configurable: https://github.com/TwiN/k8s-ttl-controller/blob/925270c76341eacca863cd84a50e53e09bf3f64a/main.go#L26 and updating the README to reflect the new feature.

There is a cache for expiration dates. https://github.com/TwiN/gatus/blob/9d151fcdb4457c537792fdfcf88ba9e82c074ede/client/client.go#L67-L72 If the domain expiration is more than 30 days away, the TTL is set to 10 days, else, it's set to 3...

@ITechGeek81 It does already try to recheck the domain expiration date if either the expiration date or the TTL is less than 24h away.

I'm sorry, I don't really understand what `send an https to host.server.tld with the http host header for server.tld` means

Just checking up again - before I can merge this, I'd like a few tests to prove that it does work as intended, and also to ensure that future changes...