Closed Rabadash8820 closed 2 years ago
So yeah, after giving this some more thought, this is how it should all work:
derploidtest.click
, www.derploidtest.click
derploid.net
, www.derploid.net
, derploid.org
, www.derploid.org
derploidtest.link
derploid.com
www.derploidtest.link
www.derploid.com
derploid.com
directly into browsers, not realizing that it redirects to the www
subdomain). And the test domains just have the checks so that the test environment stays as similar as possible to prod.<title>
of the home page, as this verifies that we didn't get an error page, and that the Jekyll builds worked correctly.HealthCheckStatus
metric (among other metrics), so each will need its own separate CloudWatch Metric in CDK, with its own separate CloudWatch Alarm (since each domain could be separately misconfigured).HealthCheckStatus
alarm in each env will have an action: notify an SNS topic with configured emails, for the case when the main domain is unhealthy but the other domains are still good due to caching. This will alert us to act before all domains are unhealthy.UnhealthyWebsiteBreakingRedirects
alarm with the rule "main domain unhealthy AND any of the (main) redirect domains unhealthy". This will spare us some alarm noise when the main website goes down: later, when the redirect domain caches expire and they start turning unhealthy, we won't get a new alarm for each domain.RedirectDomainUnhealthy
alarm with rule "main domain healthy AND any of the (main) redirect domains unhealthy". This will cause the same topic to be triggered by the same alarm anytime a (main) redirect domain is unhealthyWebsiteLatencyThresholdExceeded
alarm with rule "main domain latency OR main redirect domain latency are in alarm". This will cause the same topic to be triggered by the same alarm anytime a main (redirect) domain is taking too long.FWIW, I also considered these alternatives to Route53 HealthChecks:
This is unrelated to #33, which was about the uneducated idea of "health checking DNS records", which is not a thing. Here we're talking about adding actual health checks to the website at www.derploid.com, so that we can be notified if/when the site is down. Additional health checks for the other, "redirect" domains might still be good too, so that we know all of those rules are working correctly.