A Foglight Agent Manager (FglAM) regularly disconnects from the Foglight Management Server or the agents take a long time to connect to the FMS.
When restarting a FglAM that has hundreds of agents activated, the agents will typically all activate at the same time and then run their collections together. This can place a lot of load on a FglAM server. Many database agent collections have a 300 second interval (offline) which are roughly run in the same order. This means that intensive collections like DBSS_Databases might run on all of the agents around the same time every five minutes.
One suggestion is to start up the DB agents in batches of 20-30 agents, about every 17 seconds apart… or add the following JVM flag in the baseline.jvm.config file, then restart the FglAM.
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)
Please note: the .0 should be the next number in order higher than the previous value in the file.
If the last line in the file is vmparameter.3, then the new line should be for vmparameter.4
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.
Review KB 103160 which identifies issues with time synchronization between Virtual Machines used by Foglight environments.
Increase the current connections to the FMS as described in KB 152661
Increase the Managed Connections value to 60 as described in KB 93812
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Nutzungsbedingungen Datenschutz