You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ranger.apache.org by "Bhavik Patel (Jira)" <ji...@apache.org> on 2023/04/20 14:54:00 UTC

[jira] [Commented] (RANGER-4196) Tomcat metrics collection

    [ https://issues.apache.org/jira/browse/RANGER-4196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17714631#comment-17714631 ] 

Bhavik Patel commented on RANGER-4196:
--------------------------------------

[~vikkumar]  I think you might have gone through this: [https://www.ibm.com/docs/en/instana-observability/227?topic=technologies-monitoring-apache-tomcat] 

> 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)