Provide statistics about abuse filters (Community Wishlist/W379)
Appearance
Long-term opportunity
Description
Gathering statistical data about abuse filter efficiency and performance is currently difficult.
- Profiling data, which aggregate average run time and other information about filter performance, are scattered over dozens or hundreds of individual filter pages, with no central overview.
- Profiling data could include other statistics, like the highest amount of time needed by a filter.
- There is no indication of when a filter was last triggered. This would be useful for discovering broken or obsolete filters. Currently, it can be inferred only by examining the abuse log per filter, one by one.
- Users lost the ability to query the abuse log in the database replicas due to sensitivity of the data. What a database query could provide in a second now can be done only by querying API (e.g., using a script). This has disadvantages, such as the need for running a script with elevated permissions and potentially higher consumption of resources on the server side.
As a solution, provide a new interface exposing existing and other useful statistical data to filter maintainers.
Assigned focus area
Type of wish
Feature request
Tags
Affected users
admins, patrollers
Phabricator tasks
Other details
- Created: 19:18, 28 April 2025
- Last updated: 18:56, 9 October 2025
- Author: Matěj Suchánek (talk)
Voting