Enable Debug Logs for Starburst Trino¶

Steps to Enable Debug Logs¶

1. Navigate to the privacera-starburst-trino-plugin

   Bash
   1	cd ~/privacera-starburst-trino-plugin

2. Edit the values.yaml file

   Bash
   1	vi values.yaml

3. Add the debug log configuration to the coordinator section in values.yaml.

   Add the following configuration directly under the coordinator section:

1
2
3
4
5
6

etcFiles:
   properties:
      log.properties: |
         io.trino=INFO
         org.apache.ranger=INFO
         org.apache.ranger.authorization.trino=DEBUG

Install or Upgrade Starburst Trino on Kubernetes Cluster¶

After adding the debug log configuration to the values.yaml file, upgrade the existing Helm release—or install it if it is not already present—using the specified chart, version, and values file:

1
2
3
4
5

helm upgrade my-sep oci://harbor.starburstdata.net/starburstdata/charts/starburst-enterprise \
  --version <SBT_VERSION_TAG> \
  --install \
  --values ./values.yaml \
  --namespace <STARBURST_TRINO_NAMESPACE>

Verify Debug Logs¶

1. Wait for the pods to restart and confirm they are in Running state

   Bash
   1	kubectl get pods -n <STARBURST_TRINO_NAMESPACE>

2. Run the following command and ensure the configuration is updated

   Bash
   1	cat /etc/starburst/log.properties

3. Check the coordinator pod logs to verify that debug logs are being generated:

   Bash
   1	kubectl logs <COORDINATOR_POD_NAME> -n <STARBURST_TRINO_NAMESPACE>

Debug logging is set on the connector, not in values.yaml. Turn on Enable debug logging while configuring the connector, then set the levels:

Save the connector and download the bundle again, then rebuild the image and restart the coordinator. The levels only reach the plugin through a freshly downloaded bundle.