How to get logs from the Contrast Agents

  • Updated


In some instances, it may be necessary to collect agent logs and provide them to Contrast Support for troubleshooting purposes.


Our documentation provides details on the various Log Levels .  Depending on the issue, logging at DEBUG or TRACE level may be required to help diagnose the problem.  Contrast Support can advise further if you are unsure which level of logging is required for your issue.

The following are KBs relating to the Contrast agents and the Agent Operator.  They provide further details on how to configure logging levels and where to direct the logging output to.  You should choose the best approach depending on the set up / environment your application runs within:


Logging Configuration Properties

The following describes the logging configuration properties.  Environment variables are used by way of example.  The configuration can also be supplied via YAML or for the Java agent -D arguments.

Please consult our documentation for information on the configuration Order of precedence .

Some properties may not be supported across all agents.  The easiest way to determine the supported properties for a particular agent is use the Agent Configuration Editor .  Select an option from the "Validate using the" list for agent-specific YAML validation.



Enable diagnostic logging by setting a path to a log file. While diagnostic logging hurts performance, it generates useful information for debugging Contrast. The value set here is the location to which the agent saves log output. If no log file exists at this location, the agent creates a file. Example - /opt/Contrast/contrast.log creates a log in the /opt/Contrast directory, and rotates it automatically as needed.


Set the the log output level. Valid options are ERRORWARNINFODEBUG, and TRACE.


Set to true to redirect all logs to stdout instead of the file system.



Set to true to redirect all logs to stderr instead of the file system. May be combined with the corresponding stdout configuration to write to both streams.



Change the Contrast logger from a file-sized based rolling scheme to a date-based rolling scheme. At midnight server time, the previous day log is renamed to file_name.yyyy-MM-dd. Note - this scheme does not have a size limit; manual log pruning is required. You must set this flag to use the backups and size flags.


Set the roll size for log files in megabytes. The agent will attempt to prevent the log file from being larger than this size.


Set the number of backup files to keep. Set to 0 to disable.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request