Cloud Cruiser became HPE Consumption Analytics on Nov. 1, 2018. You'll still see the old name in places while we update this site.



Consumption Analytics Documentation

Home > Documentation for older versions > Cloud Cruiser 3 > Administering > Running jobs > Setting the job logging level

Setting the job logging level

Table of contents
No headers

Each job run creates a log file. The log file path and name are based on the process name, job name, and time of execution. All job logs are defined by the system configuration, and are located under the logs directory.

The job logging infrastructure relies on the configuration file <install_dir>/etc/ccjob-logback.xml.

You can set the overall logging level in the job configuration file or set it from the command line where you launch the job. The command line overrides the job configuration.

NOTE: Setting a level of WARN or ERROR from the command line will likely result in an empty log file and is not recommended.

The following alternate base jobs are provided to establish a default logging level other than INFO:

  • ccjob-debug
  • ccjob-trace

The following optional base steps are provided to override the logging level for a particular step:

  • ccstep-info
  • ccstep-debug
  • ccstep-trace

Logging configuration example:

<batch:job id="loggingExample" parent="ccjob-debug">
  <batch:step id="step1" next="step2" parent="ccstep-trace">

Logging override command example:

ccjob -l debug -f loggingExample

Last modified


This page has no custom tags.


This page has no classifications.