Objective

In rare scenarios, bad instrumentation causes a web server process to crash or a specific page to error out. If you ever encounter a crash or error caused by Contrast, please report the error via the Submit a Request link at the bottom of this page.

If possible, follow the steps below to gather agent logs; this additional information is vital to reproducing and fixing these types of bugs.

Process

Enable Debugging Mode

1. Connect to the traceable-proxy container

kubectl exec -it -c traceable-proxy podname-xxxx [bash or sh] -n $NAMESPACE

2. Set the log level to debug using curl

curl -X POST http://localhost:15000/logging\?level=debug

3. Exit container

Tail the traceable-proxy logs

kubectl logs podname-xxxxx -n $NAMESPACE -c traceable-proxy --follow

Collect traceable-agent logs

kubectl logs traceable-agent-xxxx -n traceableai

Disable Debugging Mode

While debug mode can help us identify issues, it is not recommended running in debug mode indefinitely. 

1. Connect to the traceable-proxy container

k exec -it -c traceable-proxy podname-xxxx [bash or sh] -n $NAMESPACE

2. Set the log level back to info using curl

curl -X POST http://localhost:15000/logging\?level=info

3. Exit container

These verbose logs will allow our support team to diagnose any issues you may encounter. To contact the Traceable Support Team, please submit a ticket to our online support portal.