You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: