Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

doc: Cleanup formatting #3017

Merged
merged 3 commits into from
Dec 2, 2020
Merged

doc: Cleanup formatting #3017

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
eb5b614
doc: Add missing backticks
jdbaldry Dec 2, 2020
d8fc98e
doc: Use absolute path to positions.yaml file
jdbaldry Dec 2, 2020
4ea172a
doc: Remove .. from URL paths
jdbaldry Dec 2, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/sources/getting-started/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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.

Expand Down