Foglight Management Server (FMS) log has entries complaining of topology limit reached:
The configured limit of 20000 instances of type HostProcess has been reached
The configured limit of 50000 instances of type DB2_Database_Partition_Table has been reached.
Foglight has a default limit of 50000 topology instances per object type.
Ideally, if the FMS has reached a topology limit, it would be best to first delete any stale objects of that type.
Reference the groovy script from KB 62094. One then runs this script passing arguments for the topology type & age in days (ie. 2 where any object two days old is deleted).
Use the dashboard to manage the stale object deletion:
To change the topology limit, we suggest setting a higher value for just the topology object of interest.
Foglight Management server should not need to be restarted for this change.
When changing the topology limit for a specific object type and searching for a topology type name it may not appear on the list as it may have a different display name.
For example, the alarm message could be "The configured limit of 50000 instances of type DBSS_Wait_Statistics has been reached.", but on the list to select a topology type the type name will appear as "SQL Server Wait Statistics" instead of "DBSS_Wait_Statistics".
To confirm the topology type display name: