System Administration > Server manager > Server manager monitoring > Teamcenter server monitoring
Teamcenter server monitoring metrics
Configure Teamcenter server monitoring using either: TC_DATA\serverMonitorConfig.xml Teamcenter Management Console You can configure the following metrics to provide specified levels of monitoring for specified threshold levels. Optionally, you can receive email notification when specified metrics cross specified thresholds. Metric Description Comment Deadlocks Report when the Teamcenter server encounters a database deadlock error. Deadlock errors should be rare, and are often transparent if handled on retry. To get more information on the Teamcenter operation involved, enable monitoring if deadlock errors are found in database server logs. VeryLongRunningQueries Report SQL, elapsed time and operation when either: Individual query time is more than the “slow” criterion. An SQL statement matches a pattern contained in the POM_SQL_PLAN environment variable. Avoid enabling during upgrade, where many queries are expected to be slow. This metric could be useful when slow query is intermittent, and so finding the Teamcenter operation context offers further clues on origin. The default "slow" criterion value is 10 seconds. This value can be overridden using the TC_SLOW_SQL environment variable. DBConnectionLosses Report when the database connection is lost. This metric is useful if a network issue is intermittent and unexpected (that is, the network issue is not due to firewall / idle-connection tidy-up or other expected event). PomLocks Report Teamcenter object locks at the end of an SOA operation. Enable this metric only for testing sessions and debugging information. POMRetries Report Teamcenter operations where database level functions failed to get a lock and retried. This event may happen frequently in busy environments and may be expected, so the metric is only appropriate for testing. Tip You should review all monitoring settings, ensuring the thresholds are set correctly for your site. If you do not know the optimum monitoring setting for any given critical event, set the value to Collect. Collect the data and review to determine normal activity levels. Then set notification values slightly higher than normal activity levels. The contents of the email notifications are generated from the TC_DATA/serverMonitorConfigInfo.xml file. This is a companion file to the serverMonitorConfig.xml file. For a complete list of possible causes and recommended actions for Teamcenter server monitoring, see this file.
Source: https://docs.sw.siemens.com/documentation/external/PL20251212545240207/en-US/tc_help/AWAdmin/fhs4814155880506/moj1737238607512/hbk1737238612021/ski1737238612989/id1385238.html · retrieved Fri Jul 31 2026 00:00:00 GMT+0000 (Coordinated Universal Time)