[
https://issues.apache.org/jira/browse/ZOOKEEPER-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dinesh Appavoo updated ZOOKEEPER-3270:
--------------------------------------
Description:
There are metrics being published for connected clients. But if we want to find
why connection count went up or down, it would be better to expose connections
per user stats. (i.e. Some auth info for the connection)
Introduce new `clnt` command which is similar to `cons` except this also
displays the user-agent to identify the type of client used to connect. List
full connection/session details for all clients connected to this server.
Includes information on numbers of packets received/sent, session id, operation
latencies, last operation performed, user-agent, etc...
was:There are metrics being published for connected clients. But if we want
to find why connection count went up or down, it would be better to expose
connections per user stats. (i.e. Some auth info for the connection)
> Publish metrics for connected clients with user stats
> -----------------------------------------------------
>
> Key: ZOOKEEPER-3270
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3270
> Project: ZooKeeper
> Issue Type: New Feature
> Components: other
> Reporter: Dinesh Appavoo
> Assignee: Dinesh Appavoo
> Priority: Major
> Labels: features
>
> There are metrics being published for connected clients. But if we want to
> find why connection count went up or down, it would be better to expose
> connections per user stats. (i.e. Some auth info for the connection)
> Introduce new `clnt` command which is similar to `cons` except this also
> displays the user-agent to identify the type of client used to connect. List
> full connection/session details for all clients connected to this server.
> Includes information on numbers of packets received/sent, session id,
> operation latencies, last operation performed, user-agent, etc...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
