CPU load when Prometheus is scraping metrics from F5 BIG-IP LTM

Hey panuwong​ 

Are you running a standalone Prometheus instance to pull the metrics from the BIG-IP, or is it part of the F5-AST setup?

In either case, take a look at whether multiple jobs are active for the same target. If an option is available, set the concurrent_workers to 1.