Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Include username in detailed connection information. #275

Open
ebusto opened this issue Jan 17, 2024 · 0 comments
Open

Include username in detailed connection information. #275

ebusto opened this issue Jan 17, 2024 · 0 comments
Labels
proposal Enhancement idea or proposal

Comments

@ebusto
Copy link

ebusto commented Jan 17, 2024

What motivated this proposal?

Our NATS cluster has a very small number of accounts, but each account has a number of distinct users. Being able to track traffic by user would be helpful when identifying heavy hitters.

What is the proposed change?

When collecting detailed connection information (when cardinality is already out the window), add auth=true as a query parameter when hitting the connz endpoint, and include the name_tag value in each corresponding metric.

Who benefits from this change?

Any NATS operator that wishes to track metrics per user, rather than (or in addition to) per account.

What alternatives have you evaluated?

Unfortunately splitting out our users into separate accounts would be a significant (breaking) change. I suspect we're not alone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
proposal Enhancement idea or proposal
Projects
None yet
Development

No branches or pull requests

1 participant