Skip to content

Commit 6147c8f

Browse files
committed
docs(collector): add Kubernetes troubleshooting using kubectl debug
1 parent 9289626 commit 6147c8f

File tree

1 file changed

+20
-0
lines changed

1 file changed

+20
-0
lines changed

content/en/docs/collector/troubleshooting.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -269,6 +269,26 @@ other component in your pipeline, it’s important to verify the following:
269269
- How is the next hop configured?
270270
- Are there any network policies that prevent data from getting in or out?
271271

272+
## Troubleshooting in Kubernetes environments
273+
274+
When running the OpenTelemetry Collector in Kubernetes, it can be useful to
275+
attach a temporary debugging container to the Collector pod to investigate
276+
networking and runtime issues.
277+
278+
Kubernetes provides the `kubectl debug` command, which allows you to create an
279+
ephemeral container that runs alongside the existing Collector container.
280+
281+
For example:
282+
283+
```bash
284+
kubectl debug -it <collector-pod-name> \
285+
--image=nicolaka/netshoot \
286+
-- /bin/bash
287+
```
288+
This approach is especially useful when diagnosing network connectivity,
289+
exporter failures, or DNS resolution issues in Kubernetes-based deployments.
290+
291+
272292
## Common Collector issues
273293

274294
This section covers how to resolve common Collector issues.

0 commit comments

Comments
 (0)