Monitors & detections
Spot an issue behind a 200 response
Combine a healthy status code with a meaningful content check.
Reviewed
Why a status code may not be enough
An endpoint can return HTTP 200 while showing an application error or reporting an unhealthy dependency. UptimeOwl evaluates your enabled content rules as well as the expected status codes.
A simple example
For the JSON below, HTTP 200 alone could pass. Set the JSON path ready, rule Must equal, and value type True. The example then reports an issue because ready is false.
{"ready":false,"message":"Database unavailable"}Keep the rule focused
Use a stable field designed to represent health. If both text and JSON rules are enabled, both must pass. Confirmation thresholds still decide when failed results become a confirmed incident.