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.

Sign up for GitHub

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

Jump to bottom

Monitoring JMX notifications #99

Open
RulerOf opened this issue Mar 1, 2022 · 0 comments
Open

Monitoring JMX notifications #99

RulerOf opened this issue Mar 1, 2022 · 0 comments
Labels
priority/long-term Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@RulerOf
Copy link

RulerOf commented Mar 1, 2022

Is your feature request related to a problem? Please describe.

I have a Java app that exposes an MBean, but it provides only operations and notifications, with no attributes.

Feature Description

The JMX integration should be able to register itself to listen for notifications, and submit those out as New Relic metrics.

Describe Alternatives

N/A

Additional context

Notifications may not translate well to time-series data. In my particular scenario, I would be served well by a simple notification count over time for each type of notification.

Priority

Nice to Have
@josemore josemore added the priority/long-term Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Mar 1, 2022
@davidgit davidgit added the triage/accepted Indicates an issue or PR is ready to be actively worked on. label Apr 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority/long-term Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@davidgit @RulerOf @josemore