diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md
index 71df0309f402158ae9b0eb0b77bb023afda7779c..84e998049e88e1348584a43cfe46ec46ede54743 100644
--- a/docs/troubleshooting.md
+++ b/docs/troubleshooting.md
@@ -23,12 +23,12 @@ In your cluster if you are running promtail as a daemonset, you will have a prom
 
 
 ```shell
-work-pc:.kube ewelch$ kubectl get pods -o wide
-NAME                                   READY   STATUS    RESTARTS   AGE   IP             NODE                                                  NOMINATED NODE
+$ kubectl get pods --all-namespaces -o wide
+NAME                                   READY   STATUS    RESTARTS   AGE   IP             NODE        NOMINATED NODE
 ...
-nginx-7b6fb56fb8-cw2cm                 1/1     Running   0          41d   10.56.4.12     gke-ops-tools1-gke-u-ops-tools1-gke-u-9d232f9e-ckgc   <none>
+nginx-7b6fb56fb8-cw2cm                 1/1     Running   0          41d   10.56.4.12     node-ckgc   <none>
 ...
-promtail-bth9q                         1/1     Running   0          3h    10.56.4.217    gke-ops-tools1-gke-u-ops-tools1-gke-u-9d232f9e-ckgc   <none>
+promtail-bth9q                         1/1     Running   0          3h    10.56.4.217    node-ckgc   <none>
 ```
 
 That output is truncated to highlight just the two pods we are interseted in, you can see with the `-o wide` flag the NODE on which they are running.
@@ -45,4 +45,4 @@ Once connected, verify the config in `/etc/promtail/promtail.yml` is what you ex
 
 Also check `/var/log/positions.yaml` and make sure promtail is tailing the logs you would expect
 
-You can check the promtail log by looking in `/var/log/containers` at the promtail container log
\ No newline at end of file
+You can check the promtail log by looking in `/var/log/containers` at the promtail container log