Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Problem/Motivation
The Purge Users module in Drupal currently generates verbose logs for each action taken during user purging, resulting in an overwhelming number of log entries, especially in scenarios with a large number of users (e.g., 10,000+ users). This verbosity makes it challenging for administrators to locate relevant logs amidst the flood of messages generated by the module.
Steps to reproduce
1. Install and enable the Purge Users module.
2. Configure the module to remove inactive users after a certain time period.
3. Monitor the log entries generated by the module, especially in environments with a large user base.
Proposed resolution
The proposed resolution is to introduce an option within the Purge Users module settings that allows administrators to control the verbosity of the generated logs. Specifically, an option should be provided to reduce the amount log entries, such as by aggregating them or providing a summary report instead of logging each individual action, or even turn them off.
User interface changes
The user interface of the Purge Users module will be updated to include a new setting related to log verbosity. This setting will allow administrators to adjust the level of detail in the generated logs.
API changes
No API changes are expected as part of this enhancement.
Data model changes
No data model changes are expected as part of this enhancement.
Issue fork purge_users-3441257
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
- 3441257-reduce-verbosity-of
compare - 3441257-add-controls-log changes, plain diff MR !24
Comments
Comment #8
mably commentedHow are we supposed to reduce that amount of logs exactly?
Comment #9
mably commentedWe could introduce a minimum log level setting.
Logs below that level wouldn't be generated.
@voide what do you think?
Comment #11
mably commentedThis issue has been in "Postponed (maintainer needs more information)" for several weeks/months with no response. I'll close it as outdated in the coming weeks unless the requested information is provided. Feel free to reopen with an update if it's still relevant.