How to set 'debug' logging on SCIM instance on Symantec Directory Management-UI Server

Products

• CA Directory

Issue/Introduction

There may be a requirement to set higher level of logging to troubleshoot SCIM related problem where the currently presented information in the log file might not be enough to find a root cause. Steps outlined below can assist in such a situation.

Resolution

You can edit the 'config-scim-default.js' file under management-ui folder (i.e. under $DXUIHOME on Linux or %DXUIHOME% on Windows) where you see a section starting with following: 

/**
 * winston logger configuration
 */

Here you will notice the default, OOTB, level is 'error'. You can change that to 'debug' and restart the SCIM server. Once done with debugging activity, make sure to revert back to level of 'error' and restart the SCIM server to reduce the extra noise in the log file.

e.g.

/**
 * winston logger configuration
 */
module.exports.winstonLoggerConfig = {
  emitError: true,
  config: {
    transports: [
      new winston.transports.File({
        level: 'error', <---Change this to 'debug'
        filename: path.join(__dirname, 'logs', 'process-id-' + process.pid + '-.log'),
        handleExceptions: true,
        humanReadableUnhandledException: true,
        json: true,
        maxsize: 100000000,
        maxFiles: 100,
        colorize: false
      }),

      new winston.transports.Console({
        level: 'error',
        handleExceptions: true,
        humanReadableUnhandledException: true,
        json: false,
        colorize: true
      })
    ],

    exitOnError: true
  }
};