This idea comes from:https://meta.discourse.org/t/how-to-block-an-ip-range-screened-ips-not-being-blocked/386851
It’s an infrequent occurrence, but when the forum gets hit by a bot/scraper/crawler attack the admin needs to quickly identify the source's IP address/range and mitigate it, without mucking about in a bunch of config files and arcane commands, especially not levels deep inside a Docker container with all the weird abstraction that takes place there.
What I am used to from other forum platforms is an admin GUI with a simple list of the users or IPs with the highest number of requests during an adjustable time window, and optionally a sorted/filtered list of which users and/or IPs occupied the highest amount of CPU time. Then once identified there is an interface to add the IP address or range to a blocklist and make it throw a 403 or 404 for requests from those IPs.
Discuss this on our forum.