Enabling Community trace in Kubernetes

About this task

The Sametime Community pod supports a variety of debug parameters as documented in Common debug parameters for Sametime Community Server. In Sametime 12, the Community debug that was formerly in the sametime.ini file is handled by a ConfigMap in Kubernetes. The debug parameters from previous releases must be modified if they are configured into the ConfigMap.

Part 1: Enable Sametime to read the debug ConfigMap
  1. Modify the values.yaml file.
    1. Change directories to where helm is located.
    2. Open values.yaml for editing.
    3. Add a new line in the global section:
      enableCommunityDebug: true/
      Note: Confirm the indentation matches the other settings (two spaces).
    4. Save and close the values.yaml.
  2. Upgrade the deployment by following the instructions in Applying configuration changes in Docker.
Part 2: Modify the ConfigMap for Community debug
  1. Modify the ConfigMap.
    1. Run the command to open the ConfigMap.
      kubectl edit cm sametime-community-logging
    2. Press i to switch to edit mode.
    3. Configure any custom debug parameters. If you know the parameter, it should be configured with the following format.
      1. The first characters are STI__DEBUG.
        Note: Enter two underscores to separate.
      2. If your debug parameters belong in the [Debug] section of the sametime.ini originally, add two underscores and then your parameter, followed by a colon and its value in quotes. For example, if setting VP_LDAP_TRACE=1 at the [Debug] section of the sametime.ini file, then the configuration setting would be: 
        STI__DEBUG__VP_LDAP_TRACE: “1”
        Note: In the example, there are two underscores between STI and DEBUG and then two more underscores before the parameter.
        If your debug setting is a component level debug such as [Debug-StUsers], then the parameter must have the same beginning STI__DEBUG, followed by a single underscore and the component name, and then two underscores and the parameter. For example, if you are setting component level debug for VP_TRACE_ALL=1 for the component [Debug-StUsers], then the configuration setting would be like this:
        STI__Debug_StUsers__VP_TRACE_ALL: "1"
    4. Save and close the ConfigMap.
  2. Scale the Community pod to apply the changes.