Skip to main content
Kate_M
Community Manager
Community Manager
Aug 19, 2024 12:31 PM UTC

How to Enable Debug Logging in Proxy Scanner

  • Apr 24, 2026 3:40 PM UTC
  • 0 replies
  • 143 views
  • Translate All
Description

You are trying to debug the proxy scanner and are having issues with auth or needing to figure out if a webhook is being received.

Scope

Any environment running the proxy scanner 

Solution

Via Docker CLI:

The best way to figure out deeper issues with the Lacework Proxy scanner is to enable debug level logging,  you can either enable it when calling the scanner and pasting the following into the command line:

-e LOG_LEVEL=debug

 

Example:

docker run -e LOG_LEVEL=debug -d --mount type=bind,source="$(pwd)"/cache,target=/opt/lacework/cache -v "$(pwd)"/config.yml:/opt/lacework/config/config.yml -p 8080:8080 lacework/lacework-proxy-scanner

This will print debug to stdout.

 

Via Helm Chart:

To enable via helm, add the following as a top level key in your values.yaml file

logLevel: debug

 

Then view by running the following

kubectl logs -n <namespace> <podname of proxy scanner>

 

Inline Scanner daemon mode

If you are running the Lacework Proxy scanner using the inline scanner binary and running it in Daemon mode (https://docs.lacework.com/integrate-inline-scanner#daemon-run-command)

 

 You can simply use the inline scanner configure commands to enable debug logging and set a log file:

lw-scanner configure logging

lw-scanner configure logging

 

 

 

Risk and Resilience in the Age of AI. An OT Thought Leadership Summit for Houston's Critical Infrastructure Leaders. Date: Thursday, December 3, 2026. Time: 8:30 am - 1:30 pm (CT). Location: The Westin Houston, Memorial City | 945 Gessner Road, Houston, TX 77024