crimson/osd: CompoundPeeringRequest tracks its start and completion too

Signed-off-by: Radosław Zarzyński <rzarzyns@redhat.com>

diff --git a/src/crimson/osd/osd_operations/compound_peering_request.cc b/src/crimson/osd/osd_operations/compound_peering_request.cc
index 286a8c0bb021dc2870743bfec1a322657606593a..86da1a47006a7999e39fbcfe46f3b70568f01a0a 100644 (file)
--- a/src/crimson/osd/osd_operations/compound_peering_request.cc
+++ b/src/crimson/osd/osd_operations/compound_peering_request.cc
@@ -125,6 +125,7 @@ void CompoundPeeringRequest::dump_detail(Formatter *f) const
 seastar::future<> CompoundPeeringRequest::start()
 {
   logger().info("{}: starting", *this);
+  track_event<StartEvent>();
   auto state = seastar::make_lw_shared<compound_state>();
   auto blocker = std::make_unique<SubOpBlocker>(
     [&] {
@@ -146,6 +147,7 @@ seastar::future<> CompoundPeeringRequest::start()
       logger().info("{}: sub events complete", *this);
       return osd.get_shard_services().dispatch_context_messages(std::move(ctx));
     }).then([this, ref=std::move(ref)] {
+      track_event<CompletionEvent>();
       logger().info("{}: complete", *this);
     });
   });