How to set logging to DEBUG level for builds in Tanzu Application Platform (TAP)

Products

• VMware Tanzu Application Platform

Issue/Introduction

When troubleshooting errors on TAP (Tanzu Application Platform), one may need more verbose logging in order to pinpoint the problem. This can arise when using the integration of TAP with Tanzu Build Service (TBS) and Supply chain:

https://docs.vmware.com/en/VMware-Tanzu-Application-Platform/1.12/tap/scc-tbs.html

You may need more detail to troubleshoot why builds are failing.

Resolution

Start TAP with the following option to get the most verbose logging:

--env BP_LOG_LEVEL=DEBUG

This setting should be configured in workload.yaml. See this doc on Migrating to the Java Cloud Native Buildpack, under "Configure the log level for buildpacks."

Also see this doc on commands to apply the TAP Supply Chain: https://docs.vmware.com/en/VMware-Tanzu-Application-Platform/1.11/tap/supply-chain-reference-workload-cli-tanzu_workload_apply.html

Additional Information

Enabling debug logging in Paketo:

https://paketo.io/docs/howto/python/#enable-debug-logging