Skip to content

Create 2025-08-15-monitor-groups-for-load-balancing.mdx #25889

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 17, 2025
Merged

Create 2025-08-15-monitor-groups-for-load-balancing.mdx #25889

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d48348e
Create 2025-08-15-monitor-groups-for-load-balancing.mdx
ncrouch-cflare Oct 16, 2025
94551d6
PCX review
Oxyjun Oct 17, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions ...ntent/changelog/load-balancing/2025-08-15-monitor-groups-for-load-balancing.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
---
title: Monitor Groups for Advanced Health Checking With Load Balancing
description: Group multiple health monitors to create sophisticated, multi-service health assessments for your pools.
date: 2025-10-16
---

Cloudflare Load Balancing now supports Monitor Groups, a powerful new way to combine multiple health monitors into a single, logical group. This allows you to create sophisticated health checks that more accurately reflect the true availability of your applications by assessing multiple services at once.
With Monitor Groups, you can ensure that all critical components of an application are healthy before sending traffic to an origin pool, enabling smarter failover decisions and greater resilience. This feature is now available via the API for customers with an Enterprise Load Balancing subscription.

### What you can do:

- **Combine Multiple Monitors**: Group different health monitors (e.g., HTTP, TCP) that check various application components, like a primary API gateway and a specific `/login` service.
- **Isolate Monitors for Observation**: Mark a monitor as "monitoring only" to receive alerts and data without it affecting a pool's health status or traffic steering. This is perfect for testing new checks or observing non-critical dependencies.
- **Improve Steering Intelligence**: Latency for Dynamic Steering is automatically averaged across all active monitors in a group, providing a more holistic view of an origin's performance.

This enhancement is ideal for complex, multi-service applications where the health of one component depends on another. By aggregating health signals, Monitor Groups provide a more accurate and comprehensive assessment of your application's true status.

For detailed information and API configuration guides, please visit our [developer documentation](/load-balancing/monitors/monitor-groups) for Monitor Groups.