From d48348ee7519def47622ece9b53d245d103ccbd8 Mon Sep 17 00:00:00 2001 From: ncrouch-cflare Date: Thu, 16 Oct 2025 15:15:48 -0400 Subject: [PATCH 1/2] Create 2025-08-15-monitor-groups-for-load-balancing.mdx --- ...08-15-monitor-groups-for-load-balancing.mdx | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 src/content/changelog/load-balancing/2025-08-15-monitor-groups-for-load-balancing.mdx diff --git a/src/content/changelog/load-balancing/2025-08-15-monitor-groups-for-load-balancing.mdx b/src/content/changelog/load-balancing/2025-08-15-monitor-groups-for-load-balancing.mdx new file mode 100644 index 000000000000000..300aca4459cca17 --- /dev/null +++ b/src/content/changelog/load-balancing/2025-08-15-monitor-groups-for-load-balancing.mdx @@ -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. From 94551d60d7fc25ab731b5c7a43b643afeda467dd Mon Sep 17 00:00:00 2001 From: Jun Lee Date: Fri, 17 Oct 2025 09:16:32 +0100 Subject: [PATCH 2/2] PCX review --- .../2025-08-15-monitor-groups-for-load-balancing.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/content/changelog/load-balancing/2025-08-15-monitor-groups-for-load-balancing.mdx b/src/content/changelog/load-balancing/2025-08-15-monitor-groups-for-load-balancing.mdx index 300aca4459cca17..dc81212e2ff4724 100644 --- a/src/content/changelog/load-balancing/2025-08-15-monitor-groups-for-load-balancing.mdx +++ b/src/content/changelog/load-balancing/2025-08-15-monitor-groups-for-load-balancing.mdx @@ -5,11 +5,12 @@ 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. +- **Combine Multiple Monitors**: Group different health monitors (for example, 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.