Liking lots of the improved audit logging recently made available in Bitbucket (logging to file, more control over what's logged, UI improvements etc), however one frustration is with the "End user activity" levels.

Referring to https://confluence.atlassian.com/bitbucketserver/audit-log-events-in-bitbucket-776640423.html (and testing in our environment)

The "Base" level for End User activity includes "Repository accessed by user" events. This accounts for 80% of our overall logged events, and while it might be considered an audit event for high compliance verticals, it's a traffic event for us (not an audit event) and just spews noise in to our audit logs. I reviewed the levels/parameters in the hopes of turning this event type off, but the only way of doing that is to change "End User activity" to Off, where ideally, we'd like to get the events logged under "End User Activity" Advanced (watchers changed/branches deleted etc), but changing to Advanced would just add these events on top of Base (Repo access).

Wondering if there's any way/plans to allow us to control exactly which events we'd like logged, either via the UI or bitbucket.properties options so we can better balance the signal/noise ratio?