1) Edge count:
Edge count is number of edges (calls between components on map) in the database.
Similar to "(.*)\|Custom Metric Process \(Virtual\)\|(.*) \| Enterprise Manager\|ApplicationTriageMap\|Database:Vertex Count" which means number of components on the map including historical records.
Solving spikes here is useless it just occupies disk space, the apm database pruning task should help the system delete any unnecessary information.
For more information about Team Center map data settings, seehttps://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/it-operations-management/application-performance-management/10-7/administrating/configure-the-workstation/application-triage-map-data-and-objects.html#concept.dita_935e6e83ce6060751531f3663e6f2331bdfab2cf_ConfigureApplicationTriageMapDataPruningConfigureApplicationTriageMapDataPruninghttps://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/it-operations-management/application-performance-management/10-7/administrating/properties-files-reference/introscopeenterprisemanager-properties.html#concept.dita_415567d672f0786bb1445983188e3bec7db9bef1_TeamCenterMapConfiguration
2) Ontology engine: Average Process Time (ms) means average time to process traces.
In case the engine is not able to process all traces, the below clamp metrics help you confirm this condition
(.*)\|Custom Metric Process \(Virtual\)\|(.*) \| Enterprise Manager\|ApplicationTriageMap\|Ontology engine\|Model Graphs Clamped
(.*)\|Custom Metric Process \(Virtual\)\|(.*) \| Enterprise Manager\|ApplicationTriageMap\|Ontology engine\|Status Changes to Database Clamped
The current thresholds in "APM Health Metric" Management module are the default values for common size customer.
If you have has more powerful hardware and larger environment, adjust the default thresholds as needed to prevent invalid alerts