Tamr Documentation

Logging in Cloud Platform Deployments

Tamr Logs

Tamr saves logs in the  <tamr_home_directory>/tamr/logs directory of the Tamr installation. Tamr logs are created for each of our microservices and the log levels of each can be configured by setting configuration variables with the unify-admin utility, see Configuring Tamr. For example the log level for "unify", the microservice for the front-end user interface of Tamr, can be adjusted using TAMR_UNIFY_LOG_LEVEL. By default, all log levels are set to INFO

Each microservice generates a <microservice>.log file and a <microservice>.request.log file. The <microservice>.log files contain broad information about the microservice, while the <microservice>.request.log tracks the API requests made to that microservice (including API requests generated by user actions in the UI).

Additional logs can also be generated depending on the microservice. If generated, the <microservice>.error.log contains ERROR level logs and <microservice>.out.log contains the standard output.

DMS Logs

Data Movement Service logs can be found in the $TAMR_UNIFY_HOME/tamr/logs directory with the format dms-*.log.

Tip: The dms-all.out.log file is a good starting point when reviewing logs.

To verify that the Data Movement Service has started successfully, after the service has started wait up to 30 seconds or check the logs for a message similar to this example:

INFO  com.tamr.apps.distro.AppsService - Framework application ready

You can also submit a request to the /api/dms/service/health API endpoint and look for a status of 200 to be returned.

Cloud Platform Service Logs

Cloud Platform

Service

Supported Documentation

AWS

Amazon EMR (Spark and Hbase)
Amazon Elasticsearch Service (Elasticsearch)
Amazon RDS (PostgreSQL)

AWS documentation

Deploying Tamr on AWS

GCP

Dataproc (Spark)
Bigtable (Hbase)
Cloud SQL (PostgreSQL)

GCP documentation

Deploying Tamr on Google Cloud Platform

Azure

Azure HDInsight (Hbase)
Azure Databricks (Spark)

Azure documentation

Deploying Tamr on Azure

See Also

Updated 3 months ago


Logging in Cloud Platform Deployments


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.