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

To include all available Mbeans under jmx mappings #8168

Closed
kathirj88 opened this issue Aug 30, 2018 · 7 comments
Closed

To include all available Mbeans under jmx mappings #8168

kathirj88 opened this issue Aug 30, 2018 · 7 comments
Labels

Comments

@kathirj88
Copy link

Would be good to have something like jmx.mappings: * to include all Mbeans without mentioning each and every Mbean which leads lot of manual work.

(And I don't see any dashboard for JMX mappings in Kibana. Would be great to have basic dashboard.)

@ruflin ruflin added the Team:Integrations Label for the Integrations team label Nov 21, 2018
@piellick
Copy link

piellick commented Jun 6, 2019

Nice request !

@exekias
Copy link
Contributor

exekias commented Jun 6, 2019

cc @jsoriano you have been thinking about something similar maybe?

@jsoriano
Copy link
Member

jsoriano commented Jun 6, 2019

We can probably do it, the trickiest thing would be to keep the mapping, we have to think more about this.
An option could be to use dynamic mapping and keep all the metrics under jmx.metrics.type.path and dedot the path. A level for the types may be needed because values returned by jmx can be of any kind.
I will start a proposal for this soon.

@ssc327
Copy link

ssc327 commented Apr 7, 2020

Has this been prioritized?

@jsoriano
Copy link
Member

jsoriano commented Apr 7, 2020

I created an issue to keep track of discussions about the dynamic mapping here #13316, but there are no specific plans yet.

@botelastic
Copy link

botelastic bot commented Mar 8, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@botelastic botelastic bot added the Stalled label Mar 8, 2021
@jsoriano jsoriano removed the Stalled label Mar 9, 2021
@botelastic
Copy link

botelastic bot commented Mar 9, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@botelastic botelastic bot added the Stalled label Mar 9, 2022
@botelastic botelastic bot closed this as completed Sep 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants