Configure Data Pipeline Logging
You can troubleshoot data pipelines using the standard logging mechanism in .
Set these log levels in consultation with Ocient Support because this setting might impact performance.
Execute these two SQL statements in this order to bump up the log message.
First, set the log level.
Then, set the level for the logging configuration.
If the log level of the first SQL statement is lower than the log level of the second SQL statement, the system loses log entries.
It is also possible to repeat the second SQL statement for different package names, such as:
- ALTER SYSTEM ALTER CONFIG SET 'streamloader.extractorEngineParameters.loggingConfig.com.ocient.extractor.allowLevel' 'Info';
- ALTER SYSTEM ALTER CONFIG SET 'streamloader.extractorEngineParameters.loggingConfig.com.ocient.extractor.en gine.allowLevel' 'Trace';
This table provides an overview of the log levels you can specify for the ALTER SYSTEM ALTER LOG LEVEL SET SQL statements with the streamloader.extractorEngineParameters.loggingConfig keys. The necessary log level for log4j must be set accordingly to at least the value specified in the column for the log4j level.
Log Level of streamloader.extractorEngineParameters.loggingConfig | Derived Level for log4j |
|---|---|
FATAL | ERROR |
ERROR | ERROR |
WARN | WARN |
INFO | INFO |
DEBUG | DEBUG |
TRACE | EDEBUG |
To reset the log level after you reproduce a problem, execute these SQL statements.