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

Improve Consumer/Producer JMX metrics collection #159

Closed
alvarocabanas opened this issue Feb 23, 2022 · 2 comments · Fixed by #178
Closed

Improve Consumer/Producer JMX metrics collection #159

alvarocabanas opened this issue Feb 23, 2022 · 2 comments · Fixed by #178
Assignees
Labels
feature request Categorizes issue or PR as related to a new feature or enhancement. priority/short-term Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@alvarocabanas
Copy link
Contributor

Right now, when setting Consumer/Producer Jmx collection the user needs to set:

  • Name: It's the consumer/producer client.id and it's difficult to know unless specifically set in the code.
  • JMX_host.
  • JMX_port.

We would like to try to auto-detect the name of the consumer/producer so the user would only need to set the host and port.

@alvarocabanas alvarocabanas added triage/accepted Indicates an issue or PR is ready to be actively worked on. priority/short-term Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Feb 25, 2022
@davidgit davidgit added the feature request Categorizes issue or PR as related to a new feature or enhancement. label Apr 21, 2022
@davidgit
Copy link
Contributor

Let's first perform a spike to agree on a solution.

@sigilioso
Copy link
Contributor

sigilioso commented Jun 27, 2022

Docs update: newrelic/docs-website#8204 @mangulonr

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Categorizes issue or PR as related to a new feature or enhancement. priority/short-term Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants