Foglight Management Server (FMS) log has entries complaining of topology limit reached:
The configured limit of 50000 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.
IMPORTANT: Ideally, if the FMS has reached a topology limit, it would be best to first delete any stale objects of the affected type. In large environments, topology limits can help to protect against cartridges generating excessive topology objects, which could lead to an overload state. If increasing the topology limit is necessary, it is recommended to monitor the JVM memory usage after the change, as the current memory allocation may be insufficient to handle the additional load and may need to be increased.
Use the dashboard to manage the stale object deletion:
For information on adding topology objects to stale object cleanup refer to How to Add Topology Objects to Stale Object Cleanup Dashboard (4255400).
To change the topology limit, we suggest setting a higher value for just the Topology Type 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:
© ALL RIGHTS RESERVED. 이용 약관 개인정보 보호정책 Cookie Preference Center