![]() You get host.name showing which machine it came from too so you can either aggregate that across all hosts or break it down by host in your visualisations. :"rver:name=UnderReplicatedPartitions,type=ReplicaManager" Now, when you want to want to lookup specific metric in Kibana to look at in Discovery or Visualize, you run the following filter like to get the data: But if it doesn't, just add another mbean mapping under jmx.mappings and it'll put a great big JSON event for every metric it captures. The example config I gave uses wildcards for the JMX metrics 'rver:type=*,name=*' so it should cover quite a lot of metrics already.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |