HTTP troubleshooting
500 Internal Server Error
The application encountered an unexpected condition while processing the request.
What 500 means for a monitor
Statixoup records an incident when 500 does not match the monitor's expected status code. Confirm the response before changing monitor rules.
Troubleshooting checklist
- 1.
Check 1
Correlate the incident with errors and traces.
- 2.
Check 2
Check recent deployments and configuration.
- 3.
Check 3
Inspect database and dependency failures.
- 4.
Check 4
Reproduce with the monitor's method and headers.
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.