I’ve been spending a lot of time in the Firewall Events section lately, mostly for audit trail reviews and incident analysis. While the data itself is incredibly valuable, I find the filtering interface to be frustratingly sluggish.
When I’m trying to narrow down to a specific ASN, IP range, or even just a date range, there’s a noticeable lag between typing, applying the filter, and seeing the results refresh. It becomes particularly cumbersome when I need to iteratively refine my search—like chasing down a specific bot pattern or verifying a rule’s impact over a few hours. This slowness turns what should be a quick investigative task into a test of patience.
I’m curious if others in the community have run into this. Is it a matter of scale (we have a high volume of events), or is this a more widespread UI/performance issue? I love the granularity Cloudflare provides, but the delay makes me hesitant to use the UI for real-time triage.
For now, I’ve resorted to pulling logs via the API for anything serious, which is a solid workaround but less accessible for quick, ad-hoc checks. Any tips or similar experiences?
Review first, buy later.
Definitely not alone in that frustration. The lag when applying date range filters is especially tough when you're trying to do iterative analysis. It feels like it defeats the purpose of having the UI for quick looks.
Have you found the API route to be consistently faster for those same iterative queries? I'm curious if the slowness is mostly in the UI rendering or if it's deeper in the query layer. I've been hesitant to build my own dashboard because I worry about hitting API rate limits.
You've hit on a key question about whether the bottleneck is in the UI or the query layer. From my own testing, the API is indeed faster for iterative filtering, which suggests the main cost is in the frontend re-rendering the entire event table on every change.
That said, while the API is faster, building a custom dashboard isn't a real solution for most teams, for exactly the reason you mention. Rate limits and maintenance overhead just shift the burden. The UI should be the optimized path. I've shared this specific feedback with the product team, noting that the filter interactions need to feel more responsive than a full API call.
Reviews build trust.