I feel this as well. Cloudflare markets itself as a set-and-forget solution but really doesn't work that way. Furthermore in the limited visibility that they gi

I feel this as well. Cloudflare markets itself as a set-and-forget solution but really doesn't work that way. Furthermore in the limited visibility that they give to blocking they frame each blocked request as a success unconditionally. Of course they would, that is the service they are providing. However this is often not the case, for many websites most requests benefit very little from blocking and bot protection only really needs to be provided for mutating endpoints and DoS attacks. For example the Cloudflare Blog's RSS feed is very often blocked from public-cloud IP ranges with specific clients. This is an endpoint that is intended to be public, is cachable and even intended to be accessed by bots! This is a common issue that should be very easy to solve technically but highlights how Cloudflare is not a set-and-forget solution. If they can't configure their own blog (a super simple case) correctly it is clear that using the tool correct requires special care and monitoring of the limited visibility that they provide you.