In an environment where a combination of database agent and Infrastructure Cartridge agents (IC) are configured to use WMI connections, any deployment of total agents exceeding 75 agents on the FglAM in any combination or mixture of those agents may cause WMI bottlenecks.
Potential WMI connection bottlenecks occurs when a total of database and infrastructure agents exceed 75 total agents on a single FglAM deployment.
This problem ONLY applies for WMINativeConnectionImpl connections which uses the JACOB library. If the agents are running WinRM, the problem should should not be encountered.
Any Linux FglAM can host up to 75 agents that are using WMI configuration. This limitation does not apply to Windows Agent Managers. Quest R&D has successfully tested up to 2000 agents using WMI (i.e. 1000 database agents + 1000 WindowsAgents) using a single Windows Agent Manager.
In Foglight Cartridge for SQL Server or Foglight Cartridge for Oracle creating a new database agent means creating an infrastructure agent along with it.
Hence up to 35 database agents - are accompanied by 35 infrastructure agents (i.e. 35 pairs of agents) can be hosted on one Linux FglAM.
Also if the agents were created manually, any combination can be chosen as long as there will be no more than 75 agents on a single Linux FglAM.
Windows registry changes are often necessary on the monitored Windows server for WMI connections from Linux-based FglAMs to be successful.
The sizing recommendation for the total amount of IC and database agents (total) using WMI limit is 75 agents per Linux Agent Manager (FglAM). This is only for agents that are configured to run against WMI connections.
WinRM is the preferred connection mechanism for monitoring Windows servers.
