User Community Service Desk Downloads
If you can't find the product or version you're looking for, visit support.ataccama.com/downloads

Logging Configuration

In on-premise deployments, the following properties are set in the etc/application.properties configuration file of each module and define where logs are outputted and in which format.

Property Data type Description

ataccama.logging.plainTextConsoleAppender

Boolean

If set to true, logs are outputted as plain text in the console.

Default value: true.

ataccama.logging.jsonConsoleAppender

Boolean

If set to true, logs are outputted in JSON format in the console.

Default value: false.

ataccama.logging.plainTextFileAppender

Boolean

If set to true, logs are outputted as plain text in the log file.

Default value: false.

ataccama.logging.jsonFileAppender

Boolean

If set to true, logs are outputted in JSON format in the log file.

You can further customize how detailed logs are and where they are stored by setting the following properties.

Property Data type Description

logging.file.path

String

The location of the shared log folder. This value is assigned to the system property LOG_PATH, which can be used for further logging configuration.

Default value: ${ataccama.path.log}.

logging.level.root

String

The root logging level. Available values are INFO, WARN, ERROR, DEBUG, OFF.

Default value: INFO.

logging.level.com.ataccama

String

The logging level for com.ataccama packages. Available values are INFO, WARN, ERROR, DEBUG.

Default value for MMM, ONE Web Application, DPM, DPE: INFO.

logging.level.com.ataccama.lib

String

Used in DPM and DPE. The logging level for com.ataccama.lib packages. Available values are INFO, WARN, ERROR, DEBUG.

Default value: INFO.

logging.level.net.javacrumbs.shedlock

String

Used in DPM. The logging level for a library used to implement synchronization for job status changes. Available values are INFO, WARN, ERROR, DEBUG.

Default value: INFO.

Unless a higher level of detail is necessary for debugging purposes, the default value (INFO) should not be changed as this causes logs to display uniqueness constraint violations in database operations, which are expected as part of the synchronization implementation of the library.

Was this page useful?