[
https://issues.apache.org/jira/browse/RANGER-4196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17757796#comment-17757796
]
Bhavik Patel commented on RANGER-4196:
--------------------------------------
Thanks [~vikkumar] .
{code:java}
"KMS": {
"GET_CURRENT_KEY_COUNT": 0,
"DELETE_KEY_ELAPSED_TIME": 0,
"EEK_DECRYPT_ELAPSED_TIME": 0,
"GET_KEYS_METADATA_ELAPSED_TIME": 0,
"EEK_GENERATE_ELAPSED_TIME": 0,
"GET_CURRENT_KEY_ELAPSED_TIME": 0,
"EEK_REENCRYPT_ELAPSED_TIME": 0,
"KEY_CREATE_COUNT": 0,
"UNAUTHORIZED_CALLS_COUNT": 0,
"KEY_CREATE_ELAPSED_TIME": 0,
"GET_KEY_VERSION_COUNT": 0,
"ROLL_NEW_VERSION_ELAPSED_TIME": 0,
"REENCRYPT_EEK_BATCH_COUNT": 0,
"REENCRYPT_EEK_BATCH_ELAPSED_TIME": 0,
"GET_KEYS_METADATA_COUNT": 0,
"GET_KEY_VERSIONS_COUNT": 0,
"GET_KEY_VERSIONS_ELAPSED_TIME": 0,
"GET_KEYS_COUNT": 0,
"EEK_GENERATE_COUNT": 0,
"INVALIDATE_CACHE_COUNT": 0,
"GET_METADATA_COUNT": 0,
"REENCRYPT_EEK_BATCH_KEYS_COUNT": 0,
"EEK_REENCRYPT_COUNT": 0,
"UNAUTHENTICATED_CALLS_COUNT": 3,
"GET_KEY_VERSION_ELAPSED_TIME": 0,
"INVALIDATE_CACHE_ELAPSED_TIME": 0,
"ROLL_NEW_VERSION_COUNT": 0,
"EEK_DECRYPT_COUNT": 0,
"GET_KEYS_METADATA_KEYNAMES_COUNT": 0,
"DELETE_KEY_COUNT": 0,
"GET_KEYS_ELAPSED_TIME": 0,
"GET_METADATA_ELAPSED_TIME": 0,
"TOTAL_CALL_COUNT": 6
}, {code}
Regarding the above output, can you perform some operations than get the
metrics and then we can actually map operations with TOTAL_CALL_COUNT
> 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)