Forum Discussion
CPU load when Prometheus is scraping metrics from F5 BIG-IP LTM
We are experiencing an issue where Prometheus is scraping metrics from F5 BIG-IP LTM, causing high CPU and memory utilization on the F5 device.
Initial step, we have adjusted the scraping interval to 1 minute, but the issue still.
Are there any recommended tuning options or best practices?
1 Reply
Which version of TMOS are you running on the BIG-IP? Are you just using Prometheus as a 'pull consumer', or do you also have a 'push consumer' configured to send telemetry to something like Elasticsearch?
Is the icrd_child on the BIG-IP showing high CPU usage? You might want to consider configuring custom endpoints as per:
CPU utilization increase after enabling Telemetry Streaming
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com