Return
-
Title
Topology churn caused by IP addresses -
Description
A large amount of topology churn is experienced in the Foglight Mangement Server caused by the IP addresses which are constantly added and removed as confirmed from the Diagnostic Snapshot.Churn details for object serverx.com(a38bf567-58e2-44e2-920d-4da9992cbfgh): Current version: 13987 Source IDs: Nubmer of recent updates: 488 Nubmer of recent changes: 486 Num changes by property: ipAddresses: 484 detail: 2 Details of recent changes: +-------------------------+-------------+---------------+--------------------+--------------------+ | Timestamp | Property | Change Type | Old Value | New Value | +-------------------------+-------------+---------------+--------------------+--------------------+ | 2017-06-01 12:25:44.537 | ipAddresses | Value Added | | 192.168.0.1 | | 2017-06-01 12:23:01.074 | ipAddresses | Value Removed | 192.168.0.1 | | 2017-06-01 12:20:46.031 | ipAddresses | Value Added | | 192.168.0.1 | | 2017-06-01 12:17:37.427 | ipAddresses | Value Removed | 192.168.0.1 | | 2017-06-01 12:13:46.325 | ipAddresses | Value Added | | 192.168.0.1 | | 2017-06-01 12:12:50.42 | ipAddresses | Value Removed | 192.168.0.1 | -
Cause
The churn was contributed by the fact that there were multiple set of physical and virtual machines with the same DNS name. -
Resolution
Normally in these cases nothing is needed to be done from Foglight side as the monitoring is normal.
A topology churn can have an performance impact on the Foglight server, so please clean up your setup and make sure you do not use duplicated DNS names or IPs.