Image Content Testing and Response Logging for HTTP Monitors
New

Content Testing and Response Logging for HTTP Monitors

We added two new features to the Website and HTTP Monitor. You can now test HTTP responses for specific content and log the response body during an incident.

Published: Tuesday, 28 July 2026

Changelog: Content Testing and Response Logging for HTTP Monitors

Summary: We added content testing and response body logging to the Website and HTTP Monitor. Verify response body text and capture full response data on incidents for faster debugging.

We added two new features to the Website and HTTP Monitor. You can now test HTTP responses for specific content and log the response body during an incident. These tools give you more visibility into the reliability of your services.

Content Testing

You can now verify the exact text of an HTTP response. The monitor checks if the response body includes a specific string or matches a pattern. This works alongside your standard status code checks to ensure your application returns the right data.

Choose from four test modes:

  • Contains
  • Does not contain
  • Matches Regex
  • Does not match Regex

Response Body Logging

You can now log the full HTTP response body when a monitor creates an incident. The system appends this data directly to the incident report. This gives your team immediate context to debug and resolve issues faster.

Quick Reference

Feature What it does
Content Testing Verify response body text with Contains, Does not contain, Matches Regex, or Does not match Regex
Response Body Logging Append the full HTTP response body to the incident report when a monitor opens an incident

Learn more in our HTTP Monitor integration guide.

Updated July 28, 2026