Monitors & detections
Know whether you are checking a redirect or its destination
Choose the behavior that matches the endpoint’s job.
Reviewed
Checking a redirect service
If an endpoint’s purpose is to redirect, disable Follow redirects and choose the expected redirect code, such as 301, in Healthy HTTP codes. That checks the original response.
Checking the destination
If you care about the destination’s health, enable Follow redirects and use codes appropriate for the final response, or monitor the final public URL directly. Up to five redirects share the check’s timeout budget.
Keep protected requests on the intended origin
Protected requests and non-GET/HEAD methods cannot follow cross-origin redirects. A redirect that works in a browser can therefore fail deliberately in a protected check. Use the intended final HTTPS endpoint.