> ## Documentation Index
> Fetch the complete documentation index at: https://docs.plerion.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting collector manager

> Resolve issues when Plerion's collector manager is not in a Ready state or when you need to retrieve logs for diagnosis.

## Collector manager not in Ready state

If the collector manager is not transitioning to a `Ready` state, follow these checks:

* Confirm the integration appears on the [Integrations page](https://app.plerion.com/settings/integrations) and [validate the release](/guides/integrations/kubernetes/collector-manager/installation/installation-validation).
* Confirm the integration status is `Active` and not `Attention Required` or `Delete In Progress`.
* Ensure the collector manager pod has DNS and internet access, as it communicates with the Plerion Control Plane over HTTPS.

Check the collector manager pod logs:

```shell theme={"system"}
kubectl logs -f plerion-collector-manager-ccbc55c5d-dr27w
```

Example output:

```
{"level":"info","ts":"2023-11-21T04:48:44Z","msg":"maxprocs: Updating GOMAXPROCS=2: determined from CPU quota"}
{"level":"info","ts":"2023-11-21T04:48:44Z","logger":"setup","msg":"initializing controller"}
{"level":"info","ts":"2023-11-21T04:48:44Z","logger":"setup","msg":"fetching tenant config"}
{"level":"error","ts":"2023-11-21T04:48:54Z","logger":"k8scbclient","msg":"request failed","error":"dial tcp: lookup au.app.plerion.com on 10.96.0.10:53: read udp 10.244.0.18:45231->10.96.0.10:53: read: connection refused"}
```

Check the DNS pods:

```shell theme={"system"}
kubectl get pods -n kube-system
```

Example output:

```
NAME                                         READY   STATUS             RESTARTS   AGE
coredns-5dd5756b68-hb4lq                     0/1     CrashLoopBackOff   6(7s ago)  4h28m
kube-proxy-lhxcq                             1/1     Running            0          4h28m
storage-provisioner                          1/1     Running            0          4h28m
```

If DNS pods are in a `Pending` or `CrashLoopBackOff` state, resolve the DNS issue first. After DNS is healthy, restart the collector manager pod and check if it becomes `Ready`.

***

## Retrieve controller logs

If the issue persists, review the collector manager logs for more detail.

1. List pods in the `plerion-system` namespace:

   ```shell theme={"system"}
   kubectl get pods -n plerion-system
   ```

   Example output:

   ```
   NAME                                           READY   STATUS    RESTARTS   AGE
   plerion-collector-manager-ccbc55c5d-dr27w      1/1     Running   0          10m
   plerion-collector-manager-ccbc55c5d-x255n      1/1     Running   0          10m
   ```

2. Retrieve logs for a specific pod (replace with the pod name you want to inspect):

   ```shell theme={"system"}
   kubectl logs -f plerion-collector-manager-ccbc55c5d-dr27w
   ```

   The `-f` flag streams logs in real time.

By reviewing these logs, you can identify connectivity or configuration issues. For deeper diagnostics, see [Enabling verbose logging](/guides/integrations/kubernetes/collector-manager/troubleshooting/enable-verbose-logging).