Beats: To include all available Mbeans under jmx mappings
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.)
kathirj88
All 5 comments
Nice request !
piellick
on 6 Jun 2019
cc @jsoriano you have been thinking about something similar maybe?
exekias
on 6 Jun 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.
jsoriano
on 6 Jun 2019
Has this been prioritized?
ssc327
on 7 Apr 2020
I created an issue to keep track of discussions about the dynamic mapping here https://github.com/elastic/beats/issues/13316, but there are no specific plans yet.
jsoriano
on 7 Apr 2020
Related issues
musayev-io
路
3Comments
nicpenning
路
3Comments
MorrieAtElastic
路
3Comments
kemra102
路
3Comments
adriansr
路
3Comments
Most helpful comment
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.pathand 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.