Foglight Agent Manager 5.9.5 - Foglight Agent Manager Guide

Resolving DATA_COLLECTION_FAILED errors

Credentials that are used by host agents to monitor remote hosts can have a Use Count policy configured through the Management Server browser interface. In such cases, when the number of collections exceeds the Use Count number, the host agent fails and enters the DATA_COLLECTION_FAILED mode. A Use Count policy violation event is also generated on the Management Server and can be viewed in the Monitor Credential Alarms dashboard.

Adjusting the maximum polling interval

The Maximum Number of Polls (per minute) property sets the maximum number of polls that Foglight accepts from Agent Manager instances per minute.

In environments with a large number of Agent Manager instances, running Foglight® with the default value of 500 for Maximum Number of Polls (per minute) can increase Agent Manager communication latency to unacceptable levels.

If you are running a large number of Agent Manager instances in your environment, Quest recommends that you change the value of this property so that it is higher than 500 (the default value). Doing so increases the number of polls allowed per minute and decreases the maximum polling interval.

To adjust the Maximum Number of Polls (per minute) setting, in the Foglight browser interface, navigate to Administration > Agents > Agent Properties > FglAM > FglAMAdapter.

CAUTION: Allowing a higher number of polls per minute increases the polling load on the Management Server. The value of Maximum Number of Polls (per minute) should only be increased on machines and in networks that can handle the increased load.

Advanced system configuration and troubleshooting

This contains platform-specific configuration information for configuring Foglight® Agent Manager on Windows® when using Windows Management Instrumentation (WMI) or Windows Remote Management (WinRM) for remote monitoring access.

NOTE: WMI and WinRM are two different mechanisms that monitoring agents can use to establish remote connections. In most scenarios, only one of these mechanisms needs to be configured. The preferred mechanism is WinRM because of WMI scalability limitations.

This also describes platform-specific instructions for configuring the Foglight Agent Manager on UNIX®.

NOTE: If your database is installed on an HP-UX server, regardless of the operating system, see Using the HP patch checking tool .

Throughout this , “the agent” is used as a placeholder for any Foglight agent that encounters these issues.

Configuring Windows Management Instrumentation (WMI)

To remotely monitor a Windows® machine, some Foglight® agents require access to the WMI services, and specifically to the WMIConnectionService. This section outlines potential issues that may be encountered by agents attempting to access WMI, and provides solutions or workarounds.

In order to access WMI, the user that the monitoring agent connects as must have sufficient credentials. Any user included in the Administrator group on the monitored machine already has the required access levels. For more information, see Minimum requirements for Windows Management Instrumentation.

There are several OS and environment-specific issues that may arise when using a Foglight agent to monitor a Windows machine remotely. This section provides solutions for the following issues: