There is high CPU utilization up to 100% on the Foglight Agent Manager (FglAM) where the database agents are running.
There is no Infobright PI repository installed directly on this server.
* Sizing and reservation issues are the most commons causes for performance issues on Foglight Agent Managers *
Insufficient sizing (CPU, memory, disk)
CPUs are not reserved if the FglAM is running on a virtual machine.
VMWare tools were not running and up to date. During investigation the FglAM was also using only 2.5 GB memory but had much more assigned.
On hosts with a high number of disks (~16K) on hosts 75-1 / 7-2, the Filesystem IO collection takes extensive resources to run iostat on the monitoring databases.
Third-party DataDirect JDBC driver conflict with the SSL connection using Java 8.
Simultaneous running of collections on numerous agents
Performance impact of MongoDB, MySQL, SSAS, or PostgreSQL database agents
Antivirus running on the FgLAM
* This is the most common resolution to this issue *
Review the Foglight for Databases deployment / sizing guide to confirm that the current FglAM sizing requirements including the number of CPUs are met
* This is the second most common resolution to this issue *
Reserve the CPUs on the Virtual Machine where the FglAM is installed as per the Deployment Guide requirements if there is an Infobright based PI repository installed.
Confirm that the VMWare tools are running on the Virtual Machine where the FglAM is installed and that the VMWare tools are up to date.
Turn off Oracle database agents in groups and/or individually to identify with agent may be causing the performance issue. Once an agent is identified, use the steps in KB article 177914 to set the Filesystem IO collection frequency to 600 to 900 seconds (10 to 15 minutes) or disable the Filesystem IO collection.
Please refer to KB 187936 regarding changing the SSL and TLS settings for SQL Server agents.
vmparameter.0 = "-Dagent.collector.schedule.load.max.delay.millis=300000";