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.

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

Logs are resend on container restart #47

Open
nilsramsperger opened this issue Oct 5, 2022 · 0 comments
Open

Logs are resend on container restart #47

nilsramsperger opened this issue Oct 5, 2022 · 0 comments

Comments

@nilsramsperger
Copy link

Hello.

I noticed that all logs are send again on container restart. That crashed my daily quota. :)
According to filebeat documentation the „registry“ prevents this problem. Unfortunately the registry is not persisted within a volume. So I tried to solve the problem by defining the volume myself. The filebeat config says that the registry is stored in /var/lib/filebeat/registry. Sadly the directory does not exist on my two container instances. Looking into the containers I found /opt/filebeat/data/registry. But I do not know, if that directory is the correct place.

It would be nice, if You could implement registry persistence.

Greetings
Nils Ramsperger

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant