Skip to content

Troubleshooting

When TestGen does not behave as expected, the application logs are the fastest way for DataKitchen support to diagnose the problem. This page explains how to collect your logs and send them to support.

Collect application logs

The application logs record what TestGen did and any errors it encountered. The simplest way to retrieve them is from within the TestGen UI.

  1. In the top-right corner of any page, open the Help menu.
  2. Select Application Logs.
  3. Optional. To retrieve logs from an earlier day, pick a day under Log Date.
  4. Click Download to save the log file to your machine.

Send logs to support

  1. Open the Help menu and select Contact Support to start an email to the DataKitchen support team.
  2. Attach the log file you downloaded.
  3. If TestGen displayed an error with a reference code, include that code. It helps support locate the matching entry in your logs.

Retrieve logs when the application is unavailable

If you cannot reach the UI, collect the logs directly from the deployment. The method depends on the install mode.

Docker mode

From the directory that contains the docker-compose.yml file, write the container logs to a file and send it to support.

docker compose logs --no-color > testgen-logs.txt

Pip mode

TestGen writes a rotating log file in the TestGen home directory, ~/.testgen/log/ by default. Send the current app.log, along with the dated app.log.YYYY-MM-DD files for any earlier days that may be relevant.

Kubernetes mode Enterprise

Write the pod logs to a file and send it to support. The examples below use the release name dk-tg-app in the datakitchen namespace.

kubectl logs deployment/dk-tg-app-testgen -n datakitchen > testgen-logs.txt

If the pod restarted, add --previous to read the logs of the instance that stopped.

kubectl logs deployment/dk-tg-app-testgen -n datakitchen --previous > testgen-logs-previous.txt

If the pod never started, describe it to see why, and include the output.

kubectl describe pod -l app.kubernetes.io/name=testgen -n datakitchen

If an install or upgrade failed, the database job keeps its logs after the failure. List the jobs to find its name, then read them.

kubectl get jobs -n datakitchen
kubectl logs job/dk-tg-app-testgen-setup-db -n datakitchen