SERVER-21776 Diagnostic logic for reads/writes should use correct log componentr3.0.9

(cherry picked from commit f210ee304a3b6eeb85a67305e6a97a32e1df3c81)

1 files changed, 2 insertions, 2 deletions

diff --git a/src/mongo/db/query/find.cpp b/src/mongo/db/query/find.cpp
index a35f69bf1f7..08cecc32813 100644
--- a/src/mongo/db/query/find.cpp
+++ b/src/mongo/db/query/find.cpp
@@ -801,7 +801,7 @@ std::string runQuery(OperationContext* txn,
                                        shardingState.getVersion(nss.ns()));
     }
 
-    const logger::LogComponent queryLogComponent = logger::LogComponent::kQuery;
+    const logger::LogComponent commandLogComponent = logger::LogComponent::kCommand;
     const logger::LogSeverity logLevelOne = logger::LogSeverity::Debug(1);
 
     PlanSummaryStats summaryStats;
@@ -816,7 +816,7 @@ std::string runQuery(OperationContext* txn,
 
     // Set debug information for consumption by the profiler.
     if (dbProfilingLevel > 0 || curop.elapsedMillis() > serverGlobalParams.slowMS ||
-        logger::globalLogDomain()->shouldLog(queryLogComponent, logLevelOne)) {
+        logger::globalLogDomain()->shouldLog(commandLogComponent, logLevelOne)) {
         // Get BSON stats.
         scoped_ptr<PlanStageStats> execStats(exec->getStats());
         BSONObjBuilder statsBob;