Kubernetes uses the Logdna agent. That's why, for Kubernetes, it should include similar steps to a basic agent troubleshooting steps.
- Make sure that agent pod is running (agent has a pod in all nodes within the cluster and watches the other pods in nodes)
They can check all the pods via kubectl get pods (here's the link for more details)
this will list all pods and their statuses. It should say "Running" for Logdna agent
- Make sure that the pod is generating the logs (if they complain logs are not coming to logdna) via
kubectl logs <podname> - Get the logdna-agent logs
- get the missing logs if that's the issue and check it pin LogDNA to confirm
Possible reasons for missing logs;
- rotated super fast before we capture those
- or generated a while back and we don't capture historic lines