This repository was archived by the owner on Dec 18, 2019. It is now read-only.
Added client/server specific memcached connection counts #9
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, we run memcached on servers that serve to multiple machines, and also runs a local client software that makes queries outbound to local or other memcached servers. mctop does not differentiate between an incoming request to the memcached instance, or an outgoing request from the client. I've added the optional flag -c or --detailed-calls which also provides a breakdown of the calls by client or server, enabled sorting of these columns, and added an option -i or --ip-address that allows the user to specify which ip memcached is listening on (by default it uses the local gateway ip address).
This has been very helpful to us in troubleshooting issues to make sure we're focusing on the proper keys, I thought it might be useful for others. I'm happy to make changes or adjustments if necessary.
Jason