Symptom
A monitor with a JSON path assertion reports the assertion failed, even though the endpoint looks healthy.
Most likely causes
- The response is not valid JSON, or the content type is not JSON.
- The path does not exist in the response body.
- The value exists but its type does not match the comparison.
- The response is larger than the inspected limit.
How to confirm
Run a manual test and read the recorded response. Compare the exact path against the returned structure. A manual test never opens an incident, so it is safe to repeat.
Resolution
- Return valid JSON with a JSON content type.
- Correct the path to match the real structure.
- Compare a scalar value (string, number, or boolean), not an object or array.
Path: $.status
Expected: ok
Returned: {"status":"ok"}What Fajita records
The result is recorded as an assertion failure. See JSON path assertions.
When to contact support
If the path and type are correct and the assertion still fails, contact support with the monitor name.