Expose more information in content node search reply trace.

This should make it easier to correlate the backend query blueprints
with the actual query terms.

1 files changed, 2 insertions, 0 deletions

diff --git a/searchcore/src/vespa/searchcore/proton/matchengine/matchengine.cpp b/searchcore/src/vespa/searchcore/proton/matchengine/matchengine.cpp
index c03ed371c4b..107f85f12d1 100644
--- a/searchcore/src/vespa/searchcore/proton/matchengine/matchengine.cpp
+++ b/searchcore/src/vespa/searchcore/proton/matchengine/matchengine.cpp
@@ -168,6 +168,8 @@ MatchEngine::performSearch(search::engine::SearchRequest::Source req)
     ret->setDistributionKey(_distributionKey);
     if ((ret->request->trace().getLevel() > 0) && ret->request->trace().hasTrace()) {
         ret->request->trace().getRoot().setLong("distribution-key", _distributionKey);
+        DocTypeName doc_type(*ret->request);
+        ret->request->trace().getRoot().setString("document-type", doc_type.getName());
         ret->request->trace().done();
         search::fef::Properties & trace = ret->propertiesMap.lookupCreate("trace");
         vespalib::SmartBuffer output(4_Ki);