Is your feature request related to a problem? Please describe.
It's hard to measure the message sent time from client perspective----the time between the call of start_send and server's reception of the message.
The background is that when TiKV's commit log duration is high but TiKV's IO and raftstore seems normal, it's hard to tell if it's because of the caller (e.g. raftclient's) bug, or the network issue or grpc crate's buffering mechanism.
Describe the solution you'd like
Provide some callback mechanism when the messages are sent in start_send.
Describe alternatives you've considered
Provide the out of box grafana metrics
Is your feature request related to a problem? Please describe. It's hard to measure the message sent time from client perspective----the time between the call of start_send and server's reception of the message. The background is that when TiKV's commit log duration is high but TiKV's IO and raftstore seems normal, it's hard to tell if it's because of the caller (e.g. raftclient's) bug, or the network issue or grpc crate's buffering mechanism.
Describe the solution you'd like Provide some callback mechanism when the messages are sent in start_send.
Describe alternatives you've considered Provide the out of box grafana metrics
Additional context None