Skip to content

Troubleshooting for Privacera Audit Server

Enable Debug Logs Using ConfigMap Changes

To enable debug logging in the Privacera Audit Server, follow the steps below:

Replace the placeholders below with the appropriate values:
  • <NS>: namespace where Privacera Manager is installed.
  • <pod>: Audit Server pod name.
  1. SSH into the instance where Privacera Manager is installed.
  2. Edit the Audit Server ConfigMap:
    Bash
    1
    kubectl edit cm auditserver-cm-conf -n <NS>

  3. Locate the PRIVACERA_LOG_LEVEL setting and set its value to DEBUG to enable detailed debug logging.

  4. Restart the Audit Server pod to apply the changes:

    Bash
    1
    kubectl delete pod <pod> -n <NS>

  5. Verify the changes:
    Bash
    1
2
    kubectl exec -it <pod>  -n <NS> -- bash
grep "PRIVACERA_LOG_LEVEL" /workdir/privacera-audit-server/conf/auditserver-env-custom.sh
  6. Navigate to the logs directory and gather the logs for debugging.
    Bash
    1
    cd /workdir/privacera-audit-server/logs

Note

  • Once you have collected and analyzed the logs, you can restore the log level to INFO by following the steps provided above.
  • Or on Restart Services the manual changes to config map will be reverted.

Comments