Agents are not collecting metrics in the main Globalview database dashboard and show N/A in workload column.
Most of the metrics are empty with no numbers and grayed out in the homepage. In the agent logs the agents appear to be collecting data successfully.
A common reason for an agent not to function as expected is topology duplication. In this scenario, the agent might have been created more than once and improperly deleted.
For example, the user has created the agent by using the installer wizard, then deleted the agent from Agent Status and created it again by using Agent Status Properties. If not properly deleted from the topology, the agent will maintain two topologies:
Note that The Topologies are created in the FMS process and agent is running on the FglAM process. That explains why the agent is marked in green in Agent Status, while there is a failure on the FMS side.
Best practices would be to create the agents from the installer wizard only.
The installer wizard will run validation checkup before allowing agent creation which may prevent agents duplication.
If an agent is green in Agent Status and is not shown in Databases Dashboard , suspect topology duplication.
When there is more than a single Agent under Instances, it means that the agent is working but the data is pushed to the wrong tree.
And if there is no data, the agent will not exist in the Databases Dashboard.
Next step would be to delete the topology for the agent in the proper way (we recommend clearing the agent and agent model data on each duplicated agent individually for performance/timeout reasons)