skip to main content
Administering Hybrid Data Pipeline : Logging
  

Try Now

Logging

Hybrid Data Pipeline comes equipped with logging capabilities. The logs produced by Hybrid Data Pipeline contain valuable information for Hybrid Data Pipeline administrators to be able to troubleshoot problems when they occur. By default, Hybrid Data Pipeline logs enough information to track the flow of events through the system and any severe errors that occur. Often, this is enough information to be able to pinpoint the problem and take corrective action. Sometimes, more information is needed, so Hybrid Data Pipeline provides a mechanism by which to configure how much diagnostic information is logged. This section explains the different logging capabilities that exist within Hybrid Data Pipeline and how to configure the different logging capabilities.
Hybrid Data Pipeline has different kinds of logs. First, there are the Tomcat logs which can be used to diagnose issues with the service usually around the ability of the service to start. The Tomcat logs also contain access logs that show which operations are being executed against the service.
Second, there are logs around the Data Access Service. For example, the log file [<user>][<data source>].<data>.log coalesces specific information about the particular data source. There will be a different log file for each user's data source. The log file [system][none].<date>.log tracks information that is not tied to a specific user or data source. The log file ddcloud.<date>.log contains information about the initialization and shutdown of the service.
For more details, see Reading a User log file .
For some data stores, Hybrid Data Pipeline also provides further logging for troubleshooting issues. These data stores include: Salesforce, Dyanmics CRM, Oracle Service Cloud, Oracle Sales Cloud, Oracle Marketing Cloud, Rollbase, SugarCRM and Google Analytics.
The following loggers can be configured for these drivers:
*Adapter: Logs events related to how Hybrid Data Pipeline communicates with the data store in question.
*SQL: Logs events associated with how the embedded SQL engine interacts with the data store and application.
*drivercommunication: Logs events associated with the JDBC calls made into the embedded SQL engine.
*cloud: Logs JDBC spy calls to troubleshoot JDBC interactions between HDP service and the data store.
Additionally, Hybrid Data Pipeline allows administrators to control the privacy level of what gets logged. For example, SQL statements are not logged by default because they may potentially contain sensitive information. Additionally, parameter and payload data is not logged by default to prevent persistence of potentially sensitive data. However, it is sometimes necessary to look at the payload data. Privacy level can be one of three values: AllowNone, AllowSQL or AllowData.
For more information, see Updating Logging Level.
For information on Logging API, see Logging API.
* Updating Logging Level
* Reading a User log file