As needed, you can modify via parameter the logging levels for the following services of the platform. These settings should only be modified when you are debugging an issue. After the issue is resolved, you should set the logging level back to its original value.
For more information on these services, see System Services and Logs.
For more information on logging levels, see https://logging.apache.org/log4j/log4j-2.6.1/manual/customloglevels.html.
You can use the following settings to mask personal information in the log files. However, doing so may complicate debugging:
| Logging Parameter and Default Value | Description |
|---|
| Code Block |
|---|
"logging.piiMask.enabled": false, |
| Set this value to true to enable masking of personally identifiable information (PII) in log files. In the , this feature masks email addresses (userIds) with hashed values. |
| Code Block |
|---|
"logging.piiMask.salt": "this is a grain of salt", |
| When PII masking is enabled, this value can be used as a randomizing element for generating hashed values. |
By default, log files for each service is automatically rotated for you.
As needed, you can enable and configure log rotation for additional log files. When enabled, the following logs are subject to rotation:
proxy_access.log
proxy_error.log
batch-job-runner.access.log
data-service.access.log
ml_service.access.log
scheduling-service.access.log
time-based-trigger-service.access.log
The following logs are excluded from log rotation and are not rotated when this feature is enabled:
- join-inf.log
- join-sel.log
- protobuf-events.log
- webapp.analytics.log
- segment-proto.log
To enable log rotation, you must copy the default configuration file into the appropriate working directory and set permissions:
| Code Block |
|---|
sudo cp /opt/trifacta/conf/trifacta-logrotate.conf /etc/logrotate.d/trifacta-logrotate.conf
sudo chown root: /etc/logrotate.d/trifacta-logrotate.conf
sudo chmod 644 /etc/logrotate.d/trifacta-logrotate.conf |
You can test the configuration using the following command:
| Code Block |
|---|
sudo logrotate --debug /etc/logrotate.d/trifacta-logrotate.conf |
The WebApp manages loading of data from the supported connections into the front-end web interface.
| Info |
|---|
NOTE: After changing these settings, the platform must be restarted. |
| Logging Parameter and Default Value | Description |
|---|
| Code Block |
|---|
"webapp.loggerOptions.silent": false, |
| When set to true, log messages are silent. |
| Code Block |
|---|
"webapp.loggerOptions.level": "info", |
| Supported levels (in decreasing order of verbosity): silly, debug, info, warning, error |
| Code Block |
|---|
"webapp.loggerOptions.json": false, |
| If set to true, logging output is in JSON format. |
| Code Block |
|---|
"webapp.loggerOptions.format": ":method :url :status :res[content-length] :response-time :referrer :remote-addr :trifacta-user :user-agent", |
| String containing list of fields to include in each log message. |
The Batch Job Runner service manages the execution of batch jobs on the backend running environment.
| Logging Parameter and Default Value | Description |
|---|
| Code Block |
|---|
"batch-job-runner.systemProperties.batch.rootLogLevel": "info", |
| Supported levels (in decreasing order of verbosity): trace, debug, info, warn, error, fatal, off |
Loads data from the various filesystems supported by the platform, both in the front-end user interface and in batch mode when Photon running environment is enabled. For more information, see Configure Photon Running Environment.
| Logging Parameter and Default Value | Description |
|---|
| Code Block |
|---|
"vfs-service.loggerOptions.silent": false, |
| When set to true, log messages are silent. |
| Code Block |
|---|
"vfs-service.loggerOptions.level": "info", |
| Supported levels (in decreasing order of verbosity): silly, debug, info, warning, error |
| Code Block |
|---|
"vfs-service.loggerOptions.json" : false, |
| If set to true, logging output is in JSON format. |
| Code Block |
|---|
"vfs-service.loggerOptions.format": ":method :url :status :res[content-length] :response-time :referrer :remote-addr :trifacta-user :user-agent", |
| String containing list of fields to include in each log message. |
Service prepares queries against JDBC interfaces, using internal REST API calls.
| Logging Parameter and Default Value | Description |
|---|
| Code Block |
|---|
"data-service.systemProperties.logging.level": "info", |
| Supported levels (in decreasing order of verbosity): trace, debug, info, warn, error, fatal, off |
| Code Block |
|---|
"data-service.systemProperties.logging.config": "classpath:logback.xml", |
| Do not modify this parameter. |
For the ML service, logging level can be modified at the command line:
| Code Block |
|---|
python cyclone.py —log-level <level> |
Supported levels: DEBUG, INFO, WARNING, ERROR, CRITICAL
| Logging Parameter and Default Value | Description |
|---|
| Code Block |
|---|
"ml-service.loggerOptions.json": false, |
| If set to true, logging output is in JSON format. |
The JSData logging options do not apply to a specific service. Instead, they are used by various services to log activities related to
and its interactions with various connections and running environments.
| Logging Parameter and Default Value | Description |
|---|
| Code Block |
|---|
"jsdata.loggerOptions.silent": false, |
| When set to true, log messages are silent. |
| Code Block |
|---|
"jsdata.loggerOptions.level": "info", |
| Supported levels (in decreasing order of verbosity): silly, debug, info, error, warn |
| Code Block |
|---|
"jsdata.loggerOptions.json": false, |
| If set to true, logging output is in JSON format. |
