Foglight Has Stopped Monitoring – Agents Not Collecting Data (Multiple Causes) (4308140)

Foglight agents are not collecting or displaying new data in the FMS console dashboards. Affected dashboards may appear outdated or empty, and monitored data is no longer updating.

• Cause 1:
  Agents are not activated in Administration | Agents | Agent Status.

• Cause 2:
  The Foglight Agent Manager (FglAM) process is not running.

• Cause 3:
  The FglAM Agent Adapter is disabled in the console.

• Cause 4:
  Resource constraints (CPU, memory, disk) or other sizing issues are impacting the stability or performance of the FglAM host.

• Cause 5:
  Network connectivity issues between FglAM and monitored hosts.

• Cause 6:
  Foglight agents are unable to authenticate with the monitored operating system or database.

• Cause 7:
  User interface (GUI) issues in the FMS console prevent data from displaying correctly.

• Cause 8:
  Performance issues on the Foglight Management Server (FMS) are causing delays or failures in data processing.

• Cause 9:
  Duplicate agent topology objects are interfering with proper data collection.

• Cause 10:
  Agent collection failures (e.g., SQL, WMI, SSH) due to environmental or configuration issues.

Resolution 1:
Navigate to Administration | Agents | Agent Status and activate any agents showing as inactive.

Resolution 2:
Log into the FglAM server (locally or remotely).
Start the FglAM process via command line or enable the Foglight Agent Manager service (or Foglight service if embedded).
If already running, restart the FglAM to resolve temporary issues.

Resolution 3:
Navigate to Administration | Agents | Agent Adapters and enable the FglAM Agent Adapter.

Resolution 4:
Verify system sizing meets deployment requirements.
Review CPU, memory, disk, VM reservations, and antivirus exclusions per the Foglight for Databases Deployment Guide.

Resolution 5:
Confirm connectivity between FglAM and monitored hosts:

• DNS name resolution

• Required firewall ports open

• Successful WMI, WinRM, or SSH connection tests

Resolution 6:
Use the agent’s “Validate Connection” feature.
Confirm login credentials are valid, not locked, and have required OS/database access.

Resolution 7:
Switch to another dashboard in the FMS UI, then return to the affected view.
Review the FMS log immediately for internal view rendering errors.

Resolution 8:
Review sizing for the FMS host using the Foglight for Databases Deployment Guide.
Ensure proper resource allocation and antivirus configuration.

Resolution 9:
Review and resolve duplicate topologies.
Refer to KB 4308990 for detailed steps on clearing duplicate topology objects.

Resolution 10:
From Administration | Agents | Agent Status, download the agent log files.
Check for SQL, WMI, or SSH collection failures.

For Further Investigation:

If the issue persists, gather the following items and contact Quest Support:

• Foglight Management Server (FMS) support bundle

• Foglight Agent Manager (FglAM) support bundle

• Screenshots of affected dashboards, including the time range (zonar) in the upper-right corner