On Thu, Jun 4, 2020, at 20:19, Cameron Kerr wrote: > > 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).
Ah - thanks for clearing up my misunderstanding. I thought I had experimented with the whitelist/blacklist and not just the filters, but my recollection is certainly faulty. I'll need to experiment with this again! -- Harald -- 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/fc4aaaab-5ba7-4035-a173-bd5bb53f8c70%40www.fastmail.com.
