From eb5b61469a3a557c0393335f2152e10d7364a35c Mon Sep 17 00:00:00 2001 From: Jack Baldry Date: Wed, 2 Dec 2020 08:58:33 +0000 Subject: [PATCH 1/3] doc: Add missing backticks Signed-off-by: Jack Baldry --- docs/sources/getting-started/troubleshooting.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/sources/getting-started/troubleshooting.md b/docs/sources/getting-started/troubleshooting.md index c5f0dff142d0..92b89ee1a3a5 100644 --- a/docs/sources/getting-started/troubleshooting.md +++ b/docs/sources/getting-started/troubleshooting.md @@ -46,11 +46,11 @@ Promtail yet. There may be one of many root causes: Promtail exposes two web pages that can be used to understand how its service discovery works. -The service discovery page (../service-discovery`) shows all +The service discovery page (`../service-discovery`) shows all discovered targets with their labels before and after relabeling as well as the reason why the target has been dropped. -The targets page (../targets`) displays only targets that are being actively +The targets page (`../targets`) displays only targets that are being actively scraped and their respective labels, files, and positions. On Kubernetes, you can access those two pages by port-forwarding the Promtail @@ -109,7 +109,7 @@ kubectl exec -it promtail-bth9q -- /bin/sh Once connected, verify the config in `/etc/promtail/promtail.yml` has the contents you expect. -Also check `/var/log/positions.yaml` (../run/promtail/positions.yaml` when +Also check `/var/log/positions.yaml` (`../run/promtail/positions.yaml` when deployed by Helm or whatever value is specified for `positions.file`) and make sure Promtail is tailing the logs you would expect. From d8fc98ebcff12b5f7ee58519662d0b7b352bfe9a Mon Sep 17 00:00:00 2001 From: Jack Baldry Date: Wed, 2 Dec 2020 09:03:30 +0000 Subject: [PATCH 2/3] doc: Use absolute path to positions.yaml file Signed-off-by: Jack Baldry --- docs/sources/getting-started/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sources/getting-started/troubleshooting.md b/docs/sources/getting-started/troubleshooting.md index 92b89ee1a3a5..2cd58674e6c1 100644 --- a/docs/sources/getting-started/troubleshooting.md +++ b/docs/sources/getting-started/troubleshooting.md @@ -109,7 +109,7 @@ kubectl exec -it promtail-bth9q -- /bin/sh Once connected, verify the config in `/etc/promtail/promtail.yml` has the contents you expect. -Also check `/var/log/positions.yaml` (`../run/promtail/positions.yaml` when +Also check `/var/log/positions.yaml` (`/run/promtail/positions.yaml` when deployed by Helm or whatever value is specified for `positions.file`) and make sure Promtail is tailing the logs you would expect. From 4ea172aae6929a0a2004e2a09df2152f4731bea1 Mon Sep 17 00:00:00 2001 From: Jack Baldry Date: Wed, 2 Dec 2020 09:10:45 +0000 Subject: [PATCH 3/3] doc: Remove .. from URL paths I'm not sure what the `..` means exactly. Signed-off-by: Jack Baldry --- docs/sources/getting-started/troubleshooting.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/sources/getting-started/troubleshooting.md b/docs/sources/getting-started/troubleshooting.md index 2cd58674e6c1..a2904b0cbb3b 100644 --- a/docs/sources/getting-started/troubleshooting.md +++ b/docs/sources/getting-started/troubleshooting.md @@ -46,11 +46,11 @@ Promtail yet. There may be one of many root causes: Promtail exposes two web pages that can be used to understand how its service discovery works. -The service discovery page (`../service-discovery`) shows all +The service discovery page (`/service-discovery`) shows all discovered targets with their labels before and after relabeling as well as the reason why the target has been dropped. -The targets page (`../targets`) displays only targets that are being actively +The targets page (`/targets`) displays only targets that are being actively scraped and their respective labels, files, and positions. On Kubernetes, you can access those two pages by port-forwarding the Promtail