Currently, logging/profiling includes read/write concern (RWC) by virtue of having been specified in the incoming command. However, when cluster-wide RWC defaults are applied to operations, they run with RWC other than the implicit server default, but appear in logs/profiling identically to operations that have not had any RWC applied (ie. have used the implicit server defaults). To avoid this misleading ambiguity, logging/profiling should include top-level readConcern and/or writeConcern fields when the RWC for the operation is something other than the implicit server default.