Add support for filtering Connections by client kind (Client, Leafnode etc) #4278
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
codegangsta
force-pushed
the
JMS-ConnzKindFiltering
branch
from
9f9214d to
f4c0674
Compare
|
This for main? |
codegangsta
force-pushed
the
JMS-ConnzKindFiltering
branch
from
f4c0674 to
cf7d947
Compare
|
@derekcollison Rebased and fixed feedback from @neilalexander. Once tests pass feel free to merge this one 😄 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds support for
kindin*ConnzOptions, which allows aConnzuser to filter returned connections by it'skindfield, namelyClientorLeafnode.This should help monitoring solutions better separate leaf node and regular client connections.