You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Brian Baynes (JIRA)" <ji...@apache.org> on 2017/09/11 20:47:00 UTC
[jira] [Updated] (GEODE-3083) New protocol should record server
statistics
[ https://issues.apache.org/jira/browse/GEODE-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Baynes updated GEODE-3083:
--------------------------------
Description:
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.
was:
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.
In particular:
- number of active clients
- time to serve a request
- anywhere else
Document the statistics being captured for inclusion in the wiki.
Summary: New protocol should record server statistics (was: New protocol should record statistics)
> 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)