This page collects a set of useful tips and tricks for troubleshooting.

Adjusting log level for Instana components

  1. Configure a component’s log level in the Core or Unit CR. In the following example, the log level is changed to DEBUG for the butler component:

      - name: butler
          - name: COMPONENT_LOGLEVEL
            # Possible values are DEBUG, INFO, WARN, ERROR (not case-sensitive)
            value: DEBUG
  2. View the logs by running the following command:

    kubectl logs <component name> -n instana-core

    where <component name> is the component name that you want to troubelshoot.

Using kubectl-specific command to debug and diagnose

The kubectl cluster-info dump command is a helpful tool for debugging and diagnosing Kubernetes clusters. It provides a detailed report on the current state of the Kubernetes cluster, including different information of resources.

Configure the target namespace and the directory to output debugging information. In the following example, the namespace is instana-units and the directory is temp. When you run this command, kubectl will generate YAML files for each resource in the instana-units namespace, and save them to the temp directory.

kubectl cluster-info dump --namespace instana-units --output-directory temp --output yaml

Here is the part of content in directory temp. You will find information details in its subdirectory instana-units about the daemonsets, deployments, events, pods and other resources in yaml file. And all the pods logs are in each pod name subdirectory which are under instana-units folder.

├── instana-units
│   ├── daemonsets.yaml
│   ├── deployments.yaml
│   ├── events.yaml
│   ├── pods.yaml
│   ├── replicasets.yaml
│   ├── replication-controllers.yaml
│   ├── services.yaml
│   ├── tu-instana-prod-appdata-legacy-converter-755bb474c7-xn4vg
│   │   └── logs.txt
│   ├── tu-instana-prod-appdata-processor-6b8f448584-nmvgl
│   │   └── logs.txt
│   ├── tu-instana-prod-filler-9485b85d-wj7pv
│   │   └── logs.txt
│   ├── tu-instana-prod-issue-tracker-bbd5f5d5f-98zxx
│   │   └── logs.txt
│   ├── tu-instana-prod-processor-fc956c46c-fxs5z
│   │   └── logs.txt
│   └── tu-instana-prod-ui-backend-89bccd9c5-8lp76
│       └── logs.txt
└── nodes.yaml


  • You can choose other namespace such as instana-core.
  • If there is no kubectl installed on your cluster, you could use oc cluster-info dump which does the same support as kubectl cluster-info dump.

More troubleshooting commands please refer to Official Document Troubleshooting Clusters through kubectl / OpenShift CLI developer command reference.