Default ProfilingLevel And Exposure of Secure data

We have the default Profiling Level enabled, which records slow operations to the diagnostic log. We really use this to improve our queries. However, we noticed that this ends up also logging our createUser commands that are taking more than 100ms and is exposing passwords. Because of this, we had to increase the 100ms to a higher value to avoid exposure of passwords. We would like to revert this back to 100ms to log our slow queries/aggregations etc. But as of now, we cannot.

Is there any way, we can configure profiling at a database level or configure to not profile “admin” database commands?

Thanks, Parvathi.