From 794c324e64c4eb2f984b0f9b1a2ac3471d4d6faa Mon Sep 17 00:00:00 2001 From: Jack Baldry Date: Wed, 2 Dec 2020 13:53:34 +0000 Subject: [PATCH] doc: Cleanup formatting (#3017) * doc: Add missing backticks Signed-off-by: Jack Baldry * doc: Use absolute path to positions.yaml file Signed-off-by: Jack Baldry * doc: Remove .. from URL paths I'm not sure what the `..` means exactly. 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 c5f0dff142..a2904b0cbb 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.