[
https://issues.apache.org/jira/browse/RANGER-4196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17757841#comment-17757841
]
Vikas Kumar commented on RANGER-4196:
-------------------------------------
[~bpatel] , Yes I will share this output from a test cluster.
Just to clarify, TOTAL_CALL_COUNT is the meter that counts all the requests
coming to this KMS instance. You won't be able to exactly match exactly with
other API call count as we don't count the health API calls plus some other
calls like many times, our request fails with 403 and then we get 200. Reason
behind this is the Kerberos authentication.
But it can be matched with access logs.
> Tomcat metrics collection
> --------------------------
>
> Key: RANGER-4196
> URL: https://issues.apache.org/jira/browse/RANGER-4196
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
> Reporter: Vikas Kumar
> Assignee: Vikas Kumar
> Priority: Major
>
> Like "JVM mterics" and other application metrics, Tomcat related metrics
> would be very useful for following use cases:
> In case client gets "SoketTimeout" or Connection refused errors, having such
> metrics at server end will really help triaging the issue.
> It should contain following metrics:
> # maxAllowedConnection
> # currentActiveConnectionCount
> # ConnectionTimeout
> # acceptCount
> # maxContainerThreadsCount
> # activeContainerThreadsCount
> # minSpareThreadsCount // corePoolSize
> And other useful metrics.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
