There is high CPU utilization up to 100% on the Foglight Agent Manager (FglAM) where the database agents are running.
There is no PI repository installed directly on this server.
* Sizing issues are the most commons causes for performance issues on Foglight Agent Managers *
Insufficient sizing (CPU, memory, disk)
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.
Issue with a specific collection or connection for one or more agents running on the FglAM. One or more agents could cause the CPU for the FglAM to spike.
For example, among Oracle agents 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
Undetermined Microsoft driver
Defect FOG-3307
FglAM issue with 6.1.0 release.
* 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
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 agents in groups and/or individually to identify with agent may be causing the performance issue. Once an agent is identified either recreate or edit the agent status properties to fix the underlying issue.
For example, in Oracle agents use the steps in KB article 4308784 to set the Filesystem IO collection frequency to 600 to 900 seconds (10 to 15 minutes) or disable the Filesystem IO collection.
Remove any override references to the older Data Direct driver from the baseline.jvmargs.config file (-Dsqlserver.driver.class.name=com.dell.dsgi.jdbc.sqlserver.SQLServerDriver) and refer to KB 4295822 regarding changing the SSL and TLS settings for SQL Server agents.
vmparameter.0 = "-Dagent.collector.schedule.load.max.delay.millis=300000";
This will spread agent activation over 5 min window (default is 2min, default collection cycle is 5min)
Deactivate any of the following types of database agents running on the agent manager.
If deactivating the agents has been found to improve the FglAM stability then these agents should be deleted and recreated on a separate FglAM.
Disable any antivirus running on the FglAM for about five minutes to determine if there is a performance impact
1). Stop FglAM
2). Edit the baseline.jvmargs.config file in the {fglam}\state\default\config folder to add a JVM (Java Virtual Machine) flag to change the driver used by the FglAM from the newer Microsoft Driver back to the Data Direct driver that used for several earlier Foglight versions. The value X should be incremented to one number higher than the highest vmparameter line in the file.
3). Restart FglAM
4). Wait 5-10 minutes for the metrics to appear and the CPU to stabilize.
Upgrade the SQL Server cartridge to 6.1.0.10 or higher.
Please contact Support for a hotfix for this issue in FglAM version 6.1.0.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Termini di utilizzo Privacy Cookie Preference Center