You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ratis.apache.org by "Shashikant Banerjee (JIRA)" <ji...@apache.org> on 2019/08/01 19:17:00 UTC
[jira] [Created] (RATIS-649) Add metrics related to ClientRequests
Shashikant Banerjee created RATIS-649:
-----------------------------------------
Summary: Add metrics related to ClientRequests
Key: RATIS-649
URL: https://issues.apache.org/jira/browse/RATIS-649
Project: Ratis
Issue Type: Sub-task
Components: server
Affects Versions: 0.4.0
Reporter: Shashikant Banerjee
Assignee: Shashikant Banerjee
Following metrics would be good to have to measure the load and the processing time of client requests:
|numReadRequestCount|Number of read type requests received on the leader|
|numWriteRequestCount|Number of write type requests received on the leader|
|numWatchForMajorityRequestCount|Number of Watch for Majority type requests received on the leader.
|
|numWatchForAllRequestCount|Number of Watch for All type requests received on the leader.|
|raftClientReadRequestLatency|Time required to process read type requests |
|raftClientWriteRequestLatency|Time required to process write type requests|
|raftClientWatchForMajority|Time required to process WatchForMajority requests|
|raftClientWatchForAllRequests|Time required to process WatchForAll requests|
|requestQueueLimitHitCount|Number of times the no of pending requests in the leader hit the configured limit.|
|numRequestRetryCacheHitCount|No of of Request Retry Cache hits. This gives an idea of retries via Raft clients because of request timeouts or exceptions.|
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)