From e9056fe2793500a569c97d9432955bd18e373ae7 Mon Sep 17 00:00:00 2001 From: Hynek Schlawack Date: Tue, 17 Oct 2023 09:48:55 +0200 Subject: [PATCH] Mention logrotate --- docs/logging-best-practices.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/logging-best-practices.md b/docs/logging-best-practices.md index 8539986d..8076cffc 100644 --- a/docs/logging-best-practices.md +++ b/docs/logging-best-practices.md @@ -7,7 +7,7 @@ Therefore let's rely on proven tools as much as possible and do only the absolut A simple but powerful approach is to log to unbuffered [standard out](https://en.wikipedia.org/wiki/Standard_out#Standard_output_.28stdout.29 ) and let other tools take care of the rest. -That can be your terminal window while developing, it can be [*systemd*](https://en.wikipedia.org/wiki/Systemd) redirecting your log entries to [*syslogd*](https://en.wikipedia.org/wiki/Syslogd), or your [cluster manager](https://kubernetes.io/docs/concepts/cluster-administration/logging/). +That can be your terminal window while developing, it can be [*systemd*](https://en.wikipedia.org/wiki/Systemd) redirecting your log entries to [*syslogd*](https://en.wikipedia.org/wiki/Syslogd) and rotate them using [*logrotate*](https://github.com/logrotate/logrotate), or your [cluster manager](https://kubernetes.io/docs/concepts/cluster-administration/logging/). It doesn't matter where or how your application is running, it just works. This is why the popular [*Twelve-Factor App* methodology](https://12factor.net/logs) suggests just that.