HTTP alerting gains granular control

Cloudflare is expanding its HTTP alerting system with new filtering and organization options, giving Enterprise customers more precise control over the traffic events they monitor. Previously, HTTP alerts were limited to a broad choice of properties and sensitivity levels, with no way to refine by path, status code, or specific IP addresses.

The upgrade is aimed at the observability use case that comes with routing traffic through Cloudflare's network. Customers can already watch for anomalies such as spikes in origin error rates; the new filters make those notifications more actionable by letting users define exactly what constitutes an alert-worthy event. For example, teams can now exclude their own test IP ranges from triggering false alarms or focus monitoring on a single path rather than an entire zone.

The new alert options support filtering and grouping on:

  • Origin response status codes
  • Edge response status codes
  • Alert sensitivity and SLO thresholds
  • Client IPv4 and IPv6 addresses
  • Individual zones

With these properties, users can ask sharper questions of their traffic data, such as which HTTP errors are breaching an SLO threshold or whether a traffic spike is traceable to internal testing. The enhanced alerts are available immediately to all Enterprise accounts and can be configured by anyone with account-level privileges.

Setting up an Advanced HTTP Alert

To create an advanced alert, navigate to the notification management section of your Cloudflare dashboard and select Advanced HTTP Alert as the notification type.

From there, you name the notification and choose both the delivery method and the recipients. Finally, pick the domains the alert applies to, then configure the desired filters, groupings, and SLO targets.

For organizations not currently on an Enterprise plan, Cloudflare's sales team can be contacted to enable access to the advanced alerting features.