我希望我们的 Route53 AWS 运行状况检查来检查页面的运行状况,不一定是目录(例如:http://xxx.xx.xxxx:80/)
这可能吗?原因是,如果我们的 lighttpd 服务器出现故障或说 wordpress 使服务器崩溃等;让它只检查一个目录(例如:http://xxx.xx.xxxx:80/)可能不会返回 500 错误....但是我们的应用程序将关闭。
我可以让它检查http://xxx.xx.xxxx:80/Page/index.php吗?
我希望我们的 Route53 AWS 运行状况检查来检查页面的运行状况,不一定是目录(例如:http://xxx.xx.xxxx:80/)
这可能吗?原因是,如果我们的 lighttpd 服务器出现故障或说 wordpress 使服务器崩溃等;让它只检查一个目录(例如:http://xxx.xx.xxxx:80/)可能不会返回 500 错误....但是我们的应用程序将关闭。
我可以让它检查http://xxx.xx.xxxx:80/Page/index.php吗?
Amazon Route 53 doesn't prevent you to check a 'page', to the contrary, it only cares about the path being a regular HTTP endpoint/resource returning respective HTTP status codes, see e.g. Creating Health Checks:
Path (HTTP Only)
The path that you want Route 53 to request when performing health checks. The path can be any value for which your endpoint will return an HTTP status code of 2xx or 3xx when the endpoint is healthy, for example, the file /docs/route53-health-check.html. Note that the leading / is required.
Please also be aware of the detailed health check specifics outlined on Managing Resource Availability with Route 53 Failover, which might affect your testing/production results, e.g. for HTTP health checks:
HTTP health checks: Route 53 must be able to establish a TCP connection with the endpoint within four seconds, and the endpoint must respond with an HTTP status code of less than 400 within two seconds.
All health checks: For a health check to change from healthy to unhealthy, it must fail three consecutive times. For a health check to change from unhealthy to healthy, it must pass three consecutive times.