Systemwide Topology Changes due to duplicate agent monitoring.
Foglight Management Server (FMS) support bundle's diagnostic snapshot shows the following symptoms
under ---- com.quest.nitro:service=Topology
+------------------------------------------------------------+-----------------------+-------------+---------------+---------------------+----------------------+
| Topology Type | Num Instance Versions | Max Version | Num Effective | Num Recent Versions | Num Recent Instances |
+------------------------------------------------------------+-----------------------+-------------+---------------+---------------------+----------------------+
The topology with a large amount in the fifth column will indicate a large amount of changes over a 7 day period
example
| HostProcess | 171302 | 69916 | 11250 | 104444 | 41 |
104444 changes over a 7 day period is quite a lot for this topology.
Note: Some topology types are known to be volatile as designed.
Just below the topology table is a section that will show the most volatile objects over the 7 day period
---------- Begin Frequent Changes for Type <Topology Name> ----------
Most volatile object: <name of object> (<Topology Name>)
Object uniqueId: abccc112-3296-4e04-9f6d-30ac532655a2
Current version: 5363
Number of object updates in period: 3376
Number of versions in period: 732
Number of recent changes: 101
Num changes by property:
monitoringAgent: 101
Details of recent changes:
+-------------------------+-----------------+--------------+------------------------------+------------------------------+
| Timestamp | Property | Change Type | Old Value | New Value |
+-------------------------+-----------------+--------------+------------------------------+------------------------------+
| 2014-11-13 08:01:30.664 | monitoringAgent | Value Change | Monitor@<host1> | Monitor@<host2> |
| 2014-11-13 08:00:28.207 | monitoringAgent | Value Change | Monitor@<host2> | Monitor@<host1> |
| 2014-11-13 07:56:28.593 | monitoringAgent | Value Change | Monitor@<host1> | Monitor@<host2> |
| 2014-11-13 07:55:26.496 | monitoringAgent | Value Change | Monitor@<host2> | Monitor@<host1> |
| 2014-11-13 07:51:26.261 | monitoringAgent | Value Change | Monitor@<host1> | Monitor@<host2> |
This example shows that the monitoringAgent property is switching between 2 agents Monitor@<host1> and Monitor@<host2> this indicates duplicate monitoring or two agents monitoring the same object.
