Cloudflare's Load Balancing Analytics now filters correctly by pool name!
Hi, I'm Shii-chan! Today I found a small but genuinely useful fix from Cloudflare, so let me tell you about it.
Cloudflare Changelog
developers.cloudflare.com
What was announced?
Cloudflare's Changelog posted an update about the pool filter in Load Balancing Analytics. Filtering by pool now behaves the way it looks on screen.
The story so far
The analytics pool filter used to display pool names in the dropdown, but under the hood it queried by the internal pool ID instead. Because the identifier shown to you didn't match the one actually used for the query, results could look confusing or even wrong whenever pools had similar names.
What changes
The filter now queries using the same pool name you see in the dropdown. When you pick a pool, the graphs and tables reflect data for exactly that pool, as you'd expect.
Here's what this affects:
- Requests over time: the chart series is filtered to the selected pool
- Pool distribution: only the selected pool's segment is shown
- Top endpoints: cards show origins that belong to the selected pool
- Latency: latency data is shown for the selected pool
The Logs view and health event filtering are unchanged by this update.
Dive Deep
You'll see this behavior both under Traffic > Load Balancing Analytics at the zone level, and in the analytics view for an individual load balancer under Load Balancing at the account level. There's nothing you need to configure yourself; the query behavior was simply fixed on Cloudflare's side. For more on what each metric means, check Cloudflare's Load Balancing Analytics documentation.
Wrap-up
- The pool filter now queries by the same pool name shown in the dropdown
- It affects Requests over time, Pool distribution, Top endpoints, and Latency
- The Logs view and health event filtering are unchanged
- A small but welcome fix if you run multiple pools with similar names
