* Causes 1 through 3 are the most common causes for Foglight Agent Manager (FglAM) performance issues with the server where the PI repository is installed. *
Insufficient resources (CPU, Memory, Disk)
CPU and/memory reservations are not set for Virtual Machines
Antivirus exclusions are not set as per the product requirements. Active virus scanning of the postgres database can cause performance issues and database corruption.
Normal activity for the PI repository processing
Defect SSDB-14157 (for SQL Server PI installations)
IO Dimension Handler, Change Tracking, and Plan Changes collections
IO or OS issue, commands like PS would not run.
Confirm that the sizing requirements detailed in the Foglight cartridge for Databases deployment guide has been met.
For Infobright PI repositories, confirm that the virtual machine CPU and memory reservations that are detailed in the Foglight cartridge for Databases deployment guide have been met. Please refer to KB 176968 for more information on these reservation settings and KB 232137 for commands that can be used to check reservations using VMWare tools from the command line.
Confirm that the required Antivirus exception requirements have been met. Details on these exceptions can be found in KB 209121.
Fog Infobright PI repositories, no issues were found with the ibengine nor there were changes following an upgrade of the database cartridge to the 126.96.36.199 level from 188.8.131.52 that may have caused the issue. The CPU spikes were expected during the interval as there are a lot of processing going on especially having so many agents monitored by PI. As the spikes do not contribute to any performance issues or overall slowness on the server, it was concluded that there is no issues to be fixed here.
This defect was fixed in the 184.108.40.206 cartridge for SQL Server and is detailed in KB 154218. Please upgrade to the latest database cartridge version which includes a fix for this issue.
*this is a temporary measure for three intensive collections that may help reduce the amount of processing done by SQL PI*
Turn off any of the follow collections for SQL Server PI agents
Reboot the Operating System and contact the System Administrator