Scaping the metrics isn't "free." There's a cost in Ignite to create them and there's a cost in Prometheus to store them.
It's a good idea to only request those you need. On Thu, 18 Jan 2024 at 05:08, Godfather <yrpati...@gmail.com> wrote: > Unfortunately we can not switch to OpenCensus. > And Yes , I have around 27 cache and I am using jmx-exporter version > 0.16.1 . > I noticed that when I use whitelistObjectNames with Mbeans that I want to > scrap then it works blazingly fast (within 1 to 2 seconds !!) > do you recommend using whitelistObjectNames or is there any other > workaround for this issue ? > > On Wed, Jan 17, 2024 at 3:23 PM Stephen Darlington <sdarling...@apache.org> > wrote: > >> I think the preference would be to use the OpenCensus exporter when using >> Prometheus, but the JMX converter should work. Do you have a lot of caches? >> I've seen lengthy "scrapes" when there are large numbers of caches. >> >> On Wed, 17 Jan 2024 at 05:14, Godfather <yrpati...@gmail.com> wrote: >> >>> Hello Community , >>> I recently upgraded to ignite 2.16 and the previous problem of jmx >>> metrics not being exported is now resolved in 2.16 . >>> However now i am trying to export ignite cache metrics , jmv metrics , >>> Partition Map Exchange metrics ,Compute Jobs metrics ,Thread Pools metrics >>> , Communication metrics, IODiscovery , IOCluster metrics with my custom >>> rules . >>> I am noticing large delay while metrics scrap (scrapinterval is 3 >>> minutes and scraptimeout is 2 minutes ) >>> >>> Is it normal to take this much time to scrap metrics through prometheus >>> jmx-exporter ? >>> Is there any way to reduce scrap time ? >>> >>> >>> sample rule for exporting cache metrics >>> - pattern: "org.apache<clsLdr=(.+), group=(cache), >>> name=(.*)><>(Cache.*):" >>> >>
