HTTP troubleshooting
400 Bad Request
The server could not understand the request due to malformed syntax or invalid parameters. In simple terms, this guide helps you understand why the response may make a monitor appear unhealthy and what to check before changing your monitor settings.
What 400 means for a monitor
Statixoup records an incident when 400 does not match the monitor's expected status code. Confirm the response before changing monitor rules.
Troubleshooting checklist
- 1.
Check 1
Validate the monitor URL and query parameters.
- 2.
Check 2
Check header formats and required fields.
- 3.
Check 3
If the endpoint expects a JSON body, ensure the request is formatted correctly.
After the service is fixed
- Confirm the URL returns the expected status without a browser session.
- Review response-time and incident history for the recovery.
- Change Expected status code only when the different response is intentional.
Avoid hiding a real outage
Changing the expected code can make an unhealthy response appear operational. Fix the service first whenever the response is unexpected.