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 contain include the following entrieslines:

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

logger.com.datamigrators.mettle.process.CommandRunner=DEBUG
logger.com.datamigrators.mettle.dsadmin.commands.DSParamsMergeCommand=DEBUG

These entries will cause any mettleci command to create a file log/stdout.log file in a subdirectory of where the current directory from which the CLI command or commands were run from. Typically this will was invoked. This will typically be under your CLI install installation directory (in the sub-directory file log/stdout.log, but it may not be located there if you are not running commands from that location (for example, case of manually executed mettleci commands) or in a different directory when invoked by pipeline agents running CLI commands will rarely be in the CLI directory). In the event of a support request you under the direction of a build pipeline. You may be asked to download provide this file and forwarded it to when raising a MettleCI support for analysisrequest.

Available Debug Loggers

...