Response assertions
Confirm that the service works correctly, not just that it responds.
The task
A service can respond with a 200 code and still return an empty list, an error in the body or stale data. A simple uptime check will not notice such an outage.
How it is solved
Response conditions are added to each monitor. A value for a condition can be picked by clicking the JSON tree of a test response, and the system suggests typical conditions itself. On failure, the history shows the expected and actual value, so there is no need to repeat the request by hand.
What is included
- Status code, response time, size, headers
- Body in JSON, XML or text, 18 comparison operators
- Regular expressions and “or” condition groups
- Creating a condition by clicking a value in the response
- Typical condition suggestions after a test run
- The same condition engine in monitors and scenario steps
Limitations
- A keyword search on a page is done with a response text condition: there is no separate check type for it.
What depends on the plan
This feature is available in every plan and has no separate limit.
Compare plansQuestions about this feature
How do I check that a page contains the right text?
Add a response text condition to the HTTP monitor: “contains” or a regular expression. For pages where the text is rendered by a script, use a browser check.
What happens if a condition is not met?
The check counts as failed, and its history keeps the expected and actual value. After the set number of consecutive failures, an alert opens.
Where it helps
Other features
All featuresCheck your services today
The free plan includes checks, a status page and a team of up to three people. The setup wizard takes you from a product to the first notification.