Timing Logs
If you suspect performance degradation, review timing logs for various components.
Default configurations already captured timings for slow components and you can check the log directory for a timing log file.
Timing logs capture action, SQL, activity, and rulebase which exceed the time limit defined in the configuration. If it detects a slow SQL, it is registered in the timing log. If simple SQLs start appearing in this log, it is an indication that the database is not performing well. If a particular activity shows up in the log, focus on that specific activity.
You can load timing logs to a database table using the sample script provided under bin or viewed through the sample projects in Spotfire. TIBCO MDM also generates alerts that you can view from the JMX console.