On Friday, 5 June 2020 05:20:55 UTC+12, Harald Koch wrote: > > On Thu, Jun 4, 2020, at 08:10, Cameron Kerr wrote: > > You should be sure to use the whitelist and blacklist features; browse the > available mbean objects using jconsole or similar to find just the bits you > will be interested in, and then query only those. > > > But that's my point - the JMX exporter queries all of your mbeans and only > then filters the results using the lists. So you'll still get the problems > you mention; locks, db queries, and so on. >
True, the default configuration is unhelpful (harmful even) in that it grabs everything, and the provided examples should do a better job of showing something more production-ready. The whitelistObjectNames and blacklistObjectNames are the bits that limit what is actually grabbed, and then the rules kick in to affect the transformation into metrics for prometheus. Even then, the white/blacklistObjectNames only apply to the MBean object itself, and not to individual Attributes, which raise its own, similar issues. (eg. if I want to monitor a thread pool I might just be interested in the current usage, rather than the status of every thread). > (Also this is an 8-month old thread :) > I realised; my reply for largely for the benefit of people who might find this in a search, as this is not yet well documented. Cheers, Cameron -- You received this message because you are subscribed to the Google Groups "Prometheus Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/25c13f1f-b96d-4a4f-9cb6-80aaafa984b5o%40googlegroups.com.
