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
Expose log files to the docker host #85
Comments
I agree about Fail2ban and am still thinking about the proper solution on the matter. However, Docker is very good at handling its logs and I believe most Freeposte containers output their logs to Docker. Instead of creating another structure for storing logs, you can use standard Docker tools. For instance, have a look at Docker log drivers like Gelf to forward logs to Splunk or ELK, or access and parse logs using |
There are already dedicated tools for extracting Docker logs, including a Logstash adapter to facilitate the ELK analysis. This part of the question is definitely out of scope for Mailu. I do think a few of the more generic logfiles, specifically those related to mail flow, could be in shared volumes instead of only in Docker logs. I know I for one still prefer |
The logstash logspout adapter is pretty much deprecated by the gelf log driver. Anyway, closing this since the question is answered. |
Being able to access log files directly on the docker host would make for easily searchable logs which could be used for fail2ban, splunk/ELK analysis etc.
freeposte/logs/{http,imap,smtp,milter,webmail,antivirus}/
Just need to make sure logs are rotated for each component.
The text was updated successfully, but these errors were encountered: