[
https://issues.apache.org/jira/browse/RANGER-4196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vikas Kumar resolved RANGER-4196.
---------------------------------
Resolution: Fixed
All the review comments were incorporated in review request:
[https://reviews.apache.org/r/74557/]
And has been merged in master with following commit link:
[https://github.com/apache/ranger/commit/f0ea284c5628ce30322245cbf07642cf5493b716]
Thanks.
> 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)
