How many Windows Agents can be deployed on one FglAM?
Parameters Used for Hardware Sizing pg 6 of 18 states that a 64bit FglAM can accommodate 150 agent instances.
Are there any restrictions that should be noted for remote monitoring?
The Foglight Agent Manager (FglAM) uses third party libraries for COM/DCOM communication depending on the connection, WMINativeConnection/WMIJavaConnection. These libraries contain code that abstracts the intricacies of the underlying Microsoft protocol. FglAM makes calls to these library APIs and It is the library's implementation of the APIs that is causing the limitations.
WinRM does not have this problem because it simply uses the HTTP/HTTPs protocol.
A single Linux Foglight Agent Manager can handle up to 75 Windows agents (either SQL Server agent or Infrastructure agents) using WMI. As a result, in Windows environments using WMI, the number of Linux Foglight Agent Managers (FglAMs) is determined by the number of Windows agents divided by 75; for example, monitoring 300 Windows agents requires at least four (4) Linux Foglight Agent Managers.
If you are monitoring more than 75 agents running on a Linux FglAM, the monitored hosts should be configured to use WinRM.
Please consult the latest version of the Foglight Agent Manager User Guide for more details on configured WMI and WinRM to monitor Windows hosts.
STATUS:
IC-1526 will be evaluated by our Product team for inclusion in a future release of Foglight.
WORKAROUND:
Enable WinRM (as detailed in the Foglight Agent Manager guide) on the target systems. WinRM is a technically superior connection protocol that requires less manipulation of the target host (registry variables) and has not exhibited a connection limitation.KB 238657 provides basic details on enabling WinRM on a target host. Please consult the latest Agent Manager for most current information.
Other recommendations include:
Manual operation workaround that essentially reduces the number of agents that start concurrently. If agents are started in smaller batches over a longer period of time, the issue does not manifest itself.
Note that the Infrastructure UnixAgent uses SSH to connect and is not affected by this issue in any way.
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center