Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Outdated release! Latest docs are Release 8.2: Configure Logging for Services

   

Contents:


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.

You can apply this change through the Admin Settings Page (recommended) or

trifacta-conf.json
. For more information, see Platform Configuration Methods.

Tip: You can download service logs through the application. See System Services and Logs.

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.

Configure

Mask PII

You can use the following settings to mask personal information in the log files. However, doing so may complicate debugging:

Logging Parameter and Default ValueDescription
"logging.piiMask.enabled": false,

Set this value to true to enable masking of personally identifiable information (PII) in log files. In the Trifacta platform, this feature masks email addresses (userIds) with hashed values.

"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.

Configure log rotation

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

NOTE: By default, these log files are rotated by supervisord. For more information on default values for stdout_logfile_maxbytes, stdout_logfile_backups, and stderr equivalents, see http://supervisord.org/configuration.html#program-x-section-values.

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:

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:

sudo logrotate --debug /etc/logrotate.d/trifacta-logrotate.conf

WebApp

The WebApp manages loading of data from the supported connections into the front-end web interface.

 

NOTE: After changing these settings, the platform must be restarted.


Logging Parameter and Default ValueDescription
"webapp.loggerOptions.silent": false,
When set to true, log messages are silent.
"webapp.loggerOptions.level": "info",
Supported levels (in decreasing order of verbosity): silly, debug, info, warning, error
"webapp.loggerOptions.json": false,

 

 

If set to true, logging output is in JSON format.
"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.

Batch Job Runner

The Batch Job Runner service manages the execution of batch jobs on the backend running environment. 

Logging Parameter and Default ValueDescription
"batch-job-runner.systemProperties.batch.rootLogLevel": "info",

Supported levels (in decreasing order of verbosity): trace, debug, info, warn, error, fatal, off 

VFS Service

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 ValueDescription
"vfs-service.loggerOptions.silent": false,
When set to true, log messages are silent.
"vfs-service.loggerOptions.level": "info",
Supported levels (in decreasing order of verbosity): silly, debug, info, warning, error
"vfs-service.loggerOptions.json" : false,
If set to true, logging output is in JSON format.
"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.

Data Service

Service prepares queries against JDBC interfaces, using internal REST API calls.

Logging Parameter and Default ValueDescription
"data-service.systemProperties.logging.level": "info",
Supported levels (in decreasing order of verbosity): trace, debug, info, warn, error, fatal, off
"data-service.systemProperties.logging.config": "classpath:logback.xml",
Do not modify this parameter.

ML Service

For the ML service, logging level can be modified at the command line:

python cyclone.py —log-level <level>

Supported levels: DEBUGINFO, WARNINGERRORCRITICAL 

Logging Parameter and Default ValueDescription
"ml-service.loggerOptions.json": false,
If set to true, logging output is in JSON format.  

JSData

The JSData logging options do not apply to a specific service. Instead, they are used by various services to log activities related to Wrangle  and its interactions with various connections and running environments. 

Logging Parameter and Default ValueDescription
"jsdata.loggerOptions.silent": false,
When set to true, log messages are silent.
"jsdata.loggerOptions.level": "info",
Supported levels (in decreasing order of verbosity): silly, debug, info, error, warn
"jsdata.loggerOptions.json": false,
If set to true, logging output is in JSON format.

  • No labels

This page has no comments.