Moodle raises several hundred events all of which are currently logged. For some sites logging every type of event is not desirable and can lead to a very large standard logstore table.

While the entire table can be cleaned and there are some 3rd party plugins to ship log entries to be archived, it would also be of benefit to admins to define which events should (and should not) be logged.

We need to decide how the UI should be presented to admins to allow them to find and decide which events should be logged. It should also be easy for them to view a summary of which events are logged etc. For this reason a text field with regex matching is not acceptable. A good place to start would be the existing event list report: https://\{your server url}/report/eventlist/index.php this report needs a bit of an update itself, but it gives an idea. The other option is report builder, but it needs to be confirmed if this can support the enable/disable "action"

As part of this solution we should be careful about performance the list of events to log (or not to log) will need to be cached so there are not additional DB reads when the logic to decided to log an event or not runs.