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

ASF subversion and git services commented on GEODE-3083:
--------------------------------------------------------

Commit 1fa67360cb8dce5be97866500c54c139bb7df289 in geode's branch 
refs/heads/feature/GEODE-3083 from [~bschuchardt]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=1fa6736 ]

Merge branch 'feature/GEODE-3083' of ssh://github.com/apache/geode into 
feature/GEODE-3083


> New protocol should record server statistics
> --------------------------------------------
>
>                 Key: GEODE-3083
>                 URL: https://issues.apache.org/jira/browse/GEODE-3083
>             Project: Geode
>          Issue Type: Sub-task
>          Components: client/server
>            Reporter: Galen O'Sullivan
>
> As a user of the new protocol, I need to be able to review accurate stats 
> related to new protocol clients as well as any existing stats impacted by new 
> clients (e.g., total client counts).
> Implement statistics for the new protocol, creating a new tree for 
> new-protocol-specific stats, but also updating relevant existing stats:
>  - client connections/threads
>  - time to serve client requests
>  - other stats impacted by new protocol clients that would be less helpful to 
> end users/admins if new protocol neglected to increment/decrement
> Specifically, have a look at {{ServerConnection}} and see where it calls into 
> its {{stats}} object. If these calls are applicable to us (at least some of 
> them are), make the same calls.
>  
> At a minimum, implement for new protocol clients:
> - Connection counts
> - Connection Starts/Stops
> - Bytes received/sent
> - Failed auth requests
> Document the statistics being captured for inclusion in the wiki.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to