Troubleshooting & Retrieve Error Logs

To troubleshoot issues that occur when using our solution for redaction, we require the following information:

1. A brief clarification on whether the issue occurs when using our solution on-prem, in our edge pipeline, or in the cloud. DNAT, Blur or Full Body Blur?
2. A short description of the issue you are facing.
3. A concise code snippet, depending on whether you are using our SDK, redact_client, or a similar tool. It is especially important to include the parameters used (e.g., --single-frame-optimization, etc.).
4. If possible, sample files that can be used to reproduce the error.
5. The error logs are essential for debugging. You can find instructions on how to retrieve them in the section below. If you are using our edge pipeline or the cloud, error logs are not required.

   ---

   
   

Retrieve Error Logs

Option 1: Download Logs via Script

• Run the following command to generate a .zip file containing all logs in the redact-enterprise-orchestration Folder
  ./download_logs.sh
• Send the resulting .zip file to your Brighter AI contact.

Option 2: Extract Logs Manually

• If you need logs for the redact-gpu container specifically, use the following command:
  docker logs redact-gpu > redact_logs.txt
• This will save the logs to a text file named redact_logs.txt.
• Send the generated file to your Brighter AI contact.

Option 3: Using Flassger

Flasgger can also be used to retrieve logs through the browser interface.

1. Open Flasgger.
2. Navigate to the Retrieve Error Logs tab ( top left corner)
3. Download the logs directly through the interface.

Need help?

If you encounter any issues during the setup, please reach out to our team. We’ll assist you during the onboarding call to ensure a smooth deployment.