Foglight has stopped monitoring, none of the agents are collecting data (multiple causes) (4308140)

Agents are not collecting or displaying new or current data in the FMS console dashboards.

Cause 1

Agents are not activated in Agent Status

Cause 2

Foglight Agent Manager is not running

Cause 3

Foglight Agent Adapter is not enabled

Cause 4

Insufficient sizing on Agent Manager server causing stability issues or performance issues.

Cause 5

Network connection issues to monitored hosts

Cause 6

Agents are unable to login to the monitored hosts

Cause 7

GUI issues in the FMS console

Cause 8

Performance issues on the FMS

Cause 9

Duplicate agent topologies

Cause 10

Collection failures gather data from the host OS or database

Resolution 1

Navigate to Administration | Agents | Agent Status and enable the agents.

Resolution 2

Open a remote (or local) session to the Foglight Agent Manager server and start the Foglight Agent Manager process from the command line (in Unix or Windows) or enabled the Windows "Foglight Agent Manager" service (or "Foglight" services if using an embedded Foglight Agent Manager).

If the Foglight Agent Manager is running, restart the FglAM to confirm if this is a temporary issue.

Resolution 3

Navigate to Administration | Agents | Agent Adapters and enable the FglAM Agent Adapter

Resolution 4

Consult the Foglight for Databases deployment guide and confirm that sizing guidelines for CPU, memory, disk space, Virtual Machine memory reservations, and Antivirus exclusions have been met on the Foglight Agent Manager.

Resolution 5

Review the network connections between the Foglight Agent Manager and the monitored hosts confirming that the hostnames can be resolved by the DNS (if servernames are used), that the required ports on firewalls between the servers are open, and WinRM or WMI connectivity is successful.

Resolution 6

Use the agent validate connection functionality and confirm with external testing that the login IDs used by the Foglight agents can successfully login to the remote host, that the userid and password is correct, and that the database or OS account is not locked out. 

Resolution 7

Navigate to a different area in the Foglight FMS console and then back to the dashboard where data is not displaying. Then immediately review the most recent updates in the FMS log to identify any new Foglight internal view errors. 

Resolution 8

Consult the Foglight for Databases deployment guide and confirm that sizing guidelines for CPU, memory, disk space, Virtual Machine memory reservations, and Antivirus exclusions have been met on the Foglight Management Server.

Resolution 9

Please review KB 68333 for details on clearing duplicate topologies for Database agents.

Resolution 10

Navigate to Administration | Agents | Agent Status and download a copy of the agent log file.

Review the log file for SQL, WMI, or SSH collection failures.

For further investigation

Generate the following items and contact Support

1. Foglight Management Server bundle
2. Foglight Agent Manager bundle
3. Screenshots of the dashboard (including the zonar timestamp/range in the top right corner of the dashboard) where the data is not displayed.