Monitors & detections
When a working endpoint reports an issue
Compare the actual check with the response you expected.
Reviewed
Read the check details first
Open the monitor’s recent results and look at the error and HTTP code. A browser loading successfully does not guarantee that a direct monitoring request receives the same response.
Check the configuration
- Confirm the public URL, method and expected HTTP codes.
- Review redirects and the timeout.
- Check whether text or JSON rules require content that is absent or has changed.
- For authenticated endpoints, verify saved credentials and required headers.
- Run a manual check and compare the new result.
Look for a different response
Authentication pages, bot protection, redirects and content generated only by browser JavaScript can explain a difference. Use a small public health endpoint where possible. Protected response logs are intentionally omitted, so diagnose secret-bearing requests without posting credentials to support.