Identifying topology volatility
- Generate an FMS Support bundle
- Open the Diagnostic Snapshot (DS) file within root directory of the FMS support bundle
- Search for "Num Recent Versions". This is one of column names of one of the Foglight tables included in the DS. The "Num Recent Versions" column has entries listing the respective number of changes a topology object - from the 1st column, i.e.
"Topology Type" - has within the past 7 days
Note: Depending on the topology type, numbers generally in the 1000+ should be monitored. - Make note of the "Topology Type" objects that have high number of "Num Recent Versions".
- Further below the table, there is a list of the top 5 most volatile topology objects. It displays the name, topology type, the property that is changing as well as how often that property is changing.
Note: Usually this will provide enough information to identify the source of the volatility.
Identifying objects that reappears in Foglight after it has been removed
Usually this is a host object that reappears.
Note: For other objects, please contact support.
- Navigation Panel| Dashboards| Administration| Tooling| Script Console
- Click on the top drop-down and select or type "Host" and press enter.
Note: Ensure "Host" is in the query field beneath the drop-down or simply type it in. - Click "Do Query"
- Select the offending host.
Note: If there are numerous objects, use the search bar, right above the listing, to filter. - Either copy the object ID in the the first column of the corresponding row or copy the Object ID in the "Object ID" field.
Using the Topology Change Logger
NOTE: The following procedure enables logging to the FMS log for identifying topology volatility. FGL-17919 provided this feature in FMS version 5.7.5.1 and higher. See example log output below.
- Log in as "foglight" user
- Open the FMS JMX console
http://:/jmx-console - Browser search for "service=TopologyChangeLogger" and select
Identifying volatility by topology type
- Type in the topology type in the "ParamValue" field for "void addTopologyChangeLoggerForType()"
Note: Use this for one topology type at a time - Let the logger run for 1 hour then generate an FMS bundle and provide to support
- To remove logging, use "void removeTopologyChangeLoggerForType()" with the "ParamValue" set for the Topology Type to be removed from logging.
Identifying volatility by object type
- Type in the Object ID in the "ParamValue" field for "void addTopologyChangeLoggerForObject()"
Note: Use this for at most 3 Object ID type at a time - Let the logger run for 1 hour then generate an FMS bundle and provide to support
- To remove logging, use "void addTopologyChangeLoggerForObject()" with the "ParamValue" set for the Object ID to be removed from logging.
Example Log Output:
2015-06-22 18:58:04.209 VERBOSE [Data-3-thread-189] com.quest.nitro.service.diagnostic.TopologyChangeLogger - Change in monitored topology object. |
type=Host; uniqueId=6549f887-46d7-417d-a53a-9607c350a699; version=5; change-type=topology.change |
Changes: |
memory: null->Memory:66918882-fe08-4530-8eef-d16062d0b225:1 |
...... |
Change submitted by agent 1 (UnixAgent@fog-2085-wsmes) on host fog-2085-wsmes |