Page Comparison

The MettleCI Command Line Interface has a debugging mode which is enabled by inserting entries in a the config.properties configuration file :In in the root directory of your CLI installation (e.g., /opt/dm/mci/cli

Enable debugging by updating the file to include the following lines:

# Setting the log level for a specific logger takes the format:
#     logger.[LOG_NAME]=[LOG_LEVEL]

logger.Shell=DEBUG
logger.Command.com.datamigrators.mettle.process.CommandRunner=DEBUG
logger.com.datamigrators.mettle.dsadmin.processcommands.CommandRunnerDSParamsMergeCommand=DEBUG

If you are asked to enable debug logging for a specific logger by support, you will need to add a line to the config.properties file, following the format described above. You can find the log file in your CLI install in the location log/stdout.log, which you can then send to MettleCI support.These entries will cause any mettleci command to create a file log/stdout.log file in the current directory from which the CLI command was invoked. This will typically be under your CLI installation directory (in the case of manually executed mettleci commands) or in a different directory when invoked by pipeline agents running CLI commands under the direction of a build pipeline. You may be asked to provide this file when raising a MettleCI support request.

Available Debug Loggers