I was looking through the logs on some of my Promtail instances and noticed many messages like these:
level=info ts=2022-08-24T16:57:15.154189336Z caller=tailer.go:202 component=tailer msg="skipping update of position for a file which does not currently exist" path=/var/lib/nomad/alloc/f41f71e51/alloc/logs/app.stderr.43 level=info ts=2022-08-24T16:57:15.154207279Z caller=tailer.go:202 component=tailer msg="skipping update of position for a file which does not currently exist" path=/var/lib/nomad/alloc/f41f71e51/alloc/logs/app.stderr.150
These messages will be repeated numerous times, even for the for the same log (
app.stderr.150). This means that it is not just reporting that the file has gone missing, it is continuing to retry the position update unsuccessfully. Obviously they are
info level logs and not
I am wondering if there is a way to configure Promtail so that it handles this situation properly. Or is this the expected and proper way to handle logs that have been rotated?