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

Closed
senilio opened this Issue Oct 19, 2016 · 3 comments

Comments

3 participants
@senilio
Copy link

senilio commented Oct 19, 2016

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.

@kaiyou

This comment has been minimized.

Copy link
Member

kaiyou commented Oct 19, 2016

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 docker logs or the JSON files in /var/log/docker.

@curry684

This comment has been minimized.

Copy link
Member

curry684 commented Oct 27, 2016

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 grep over Kibana for debugging why a mail wasn't received by someone.

@kaiyou

This comment has been minimized.

Copy link
Member

kaiyou commented Oct 28, 2016

The logstash logspout adapter is pretty much deprecated by the gelf log driver. Anyway, closing this since the question is answered.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment