nickslowinski/mailcow-dockerized-docs
1
0
Fork 0
Code Issues Pull-Requests Projekte Releases Pakete Wiki Aktivität

fail2ban to netfilter

Quellcode durchsuchen
Dieser Commit ist enthalten in:
Phoenix Eve Aspacio 2018-05-10 12:10:53 +08:00 committet von GitHub
Ursprung 9e9be1879e
Commit 6e7726346d
Es konnte kein GPG-SchlĂĽssel zu dieser Signatur gefunden werden
GPG-SchlĂĽssel-ID: 4AEE18F83AFDEB23
1 geänderte Dateien mit 2 neuen und 2 gelöschten Zeilen
Statistiken anzeigen Patch-Datei herunterladen Diff-Datei herunterladen Alle Dateien ausklappen Alle Dateien einklappen

4
docs/firststeps-logging.md
Datei anzeigen

@ -14,12 +14,12 @@ The **default logging driver is "json"**.
Some logs are filtered and written to Redis keys but also streamed to a Redis channel. Some logs are filtered and written to Redis keys but also streamed to a Redis channel.
The Redis channel is used to stream logs with failed authentication attempts to be read by fail2ban-mailcow. The Redis channel is used to stream logs with failed authentication attempts to be read by netfilter-mailcow.
The Redis keys are persistent and will keep 10000 lines of logs for the web UI. The Redis keys are persistent and will keep 10000 lines of logs for the web UI.
This mechanism makes it possible to use whatever Docker logging driver you want to, without losing This mechanism makes it possible to use whatever Docker logging driver you want to, without losing
the ability to read logs from the UI or ban suspicious clients with fail2ban-mailcow. the ability to read logs from the UI or ban suspicious clients with netfilter-mailcow.
Redis keys will only hold logs from applications and filter out system messages (think of cron etc.). Redis keys will only hold logs from applications and filter out system messages (think of cron etc.).