Skip to content

Enable Debug Logs for Trino

This section explains how to enable debug logs for Trino to assist with troubleshooting access management issues.

  1. Navigate to the privacera-trino-plugin

    Bash
    1
    cd ~/privacera-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

    YAML
    1
2
3
4
5
6
7
    coordinator:
  etcFiles:
    properties:
      log.properties: |
        io.trino=INFO
        org.apache.ranger=INFO
        org.apache.ranger.authorization.trino=DEBUG

  4. Save the values.yaml file.

  5. Install or Upgrade Trino on Kubernetes Cluster

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

    Bash
    1
    helm upgrade -f values.yaml privacera-trino-cluster trino/trino --namespace=<TRINO_NAMESPACE>

Verify Debug Logs

  1. Wait for the pods to restart and verify they are in Running state
    Bash
    1
    kubectl get pods -n <TRINO_NAMESPACE>
  2. Run the following command and ensure the configuration is updated
    Bash
    1
    cat /etc/trino/log.properties
  3. Check the coordinator pod logs to verify debug logs are being generated
    Bash
    1
    kubectl logs <COORDINATOR_POD_NAME> -n <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:

Field Definition Default
Plugin log level Level for the Privacera plugin classes. INFO
Trino log level Level for everything else on the cluster. INFO
Ranger log level Level for the Ranger policy engine and audit client. INFO

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.