[ https://issues.apache.org/jira/browse/RATIS-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aravindan Vijayan updated RATIS-649: ------------------------------------ Attachment: RATIS-649-002.patch > 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: Aravindan Vijayan > Priority: Major > Attachments: RATIS-649-000.patch, RATIS-649-001.patch, > RATIS-649-002.patch > > > 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 (v8.3.4#803005)