Raise the logging visibility of selected database requests

For easier troubleshooting, you can dictate that certain database requests get logged in a handy central log file.

For example, database requests that run longer than 10 seconds are likely candidates for troubleshooting. You can have such requests automatically logged in the vamessages.log file for your inspection. The exact length of time after which a request becomes problematic depends on your environment.

How it works:

All database queries are logged at DEBUG level by default.
By default, the vamessages.log file is configured to include all events logged at the INFO level or higher.
Database queries that run over a configurable time limit are logged at INFO rather than DEBUG, which causes them to appear in vamessages.log.

Stop TeamForge.
- Stop Apache on RHEL/CentOS: /etc/init.d/httpd stop
- Stop PostgreSQL on RHEL/Centos: /etc/init.d/postgresql-9.6 stop
- Stop TeamForge: /etc/init.d/collabnet stop
Open the site-options.conf file, the master configuration file that controls your TeamForge site.
- vi /opt/collabnet/teamforge/etc/site-options.conf
Note: vi is an example. Any *nix text editor will work.
In the site-options.conf file, change the value of the LOG_QUERY_TIME_THRESHOLD variable to a value, in milliseconds, that makes sense for your environment.
Deploy services.
- /opt/collabnet/teamforge/bin/teamforge provision
Note:
The "provision" command prompts for response before it bootstraps or migrates data during TeamForge installation and upgrade respectively. Enter "y" or "N" to proceed. For more information, see the TeamForge script.

TeamForge 17.4 (and later) installer expects the system locale to be LANG=en_US.UTF-8. TeamForge "provision" command fails otherwise.
Start TeamForge.
- /etc/init.d/httpd start
- /etc/init.d/postgresql-9.2 start
- /etc/init.d/collabnet start