Skip to content
Snippets Groups Projects
Unverified Commit 3beb259e authored by David's avatar David Committed by GitHub
Browse files

Update troubleshooting.md

parent 5b7057db
No related branches found
No related tags found
No related merge requests found
......@@ -10,6 +10,14 @@ This can have several reasons:
- Promtail started sending logs before Loki was ready. This can happen in test environments where promtail already read all logs and sent them off. Here is what you can do:
- Generally start promtail after Loki, e.g., 60 seconds later.
- Restarting promtail will not necessarily resend log messages that have been read. To force sending all messages again, delete the positions file (default location `/tmp/positions.yaml`) or make sure new log messages are written after both promtail and Loki have started.
- Promtail is ignoring targets because of a configuration rule
- Detect this by turning on debug logging and then look for `dropping target, no labels` or `ignoring target` messages.
## Debug output
Both binaries support a log level parameter on the command-line, e.g.: `loki —log.level= debug ...`
## No labels:
## Failed to create target, "ioutil.ReadDir: readdirent: not a directory"
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment