search

mailcow / mailcow-dockerized

mailcow: dockerized - 🐮 + 🐋 = 💕
https://mailcow.email
GNU General Public License v3.0
8.31k stars 1.13k forks source link

ELK stack / logging #2786

Open strarsis opened 5 years ago

strarsis commented 5 years ago

Is your feature request related to a problem? Please describe. Advanced logging analysis, finding trends, attacks, spamming, predicting disk space shortages, bandwidth issues, traffic overconsumption

Describe the solution you'd like Support for ELK stack for all mailcow dockerized services, so an ELK stack docker setup can be connected to it (either on same system or another one).

patschi commented 5 years ago

Docker by default logs all container output to /var/lib/docker/containers/. You can use any application or scripts to get this output and forward it to any log management of your choice, to further process the logs there. (I'm doing that this way without issues). The only negative side is that you're required to parse the JSON at some point.

strarsis commented 4 years ago

There is some log information that is notably useful for the postmaster: Rejected outbound mail due to valid issues like being blacklisted, SPF/DKIM/TLS error with other MTAs. Rejected inbound mail due to alias ownership/repeated failed login attempts from the same IP over days (which are probably legitimate login attempts that fail because of MUA config issues). Lots of unusual outbound mail (compromised mail account, spamming and viruses).

Some ELK filter/rules suite for mailcow would be awesome!

patschi commented 4 years ago

I'm sure it would be very useful and nice-to-know, but I believe it might be a bit out-of-scope of the core mailcow development. If some user wants to contribute some templates/filter/rule-sets for a ELK stack, I think the docs might be a good choice.