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:

  1. 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
  2. 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.
  3. 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.
  4. Deploy services.
    • /opt/collabnet/teamforge/bin/teamforge provision

    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.

  5. Start TeamForge.
    • /etc/init.d/httpd start
    • /etc/init.d/postgresql-9.2 start
    • /etc/init.d/collabnet start