Logrotate: Difference between revisions
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
Logrotate is a utility that rotates logs. Log rotation simply means to rename an existing log file to something else, thereby keeping the log file sizes tenable. Logrotate makes it easy to define log rotation rules, such as how many old logs to keep and for how long, the size a log should be before it's rotated, any post-rotation commands it needs to run, and more. | Logrotate is a utility that rotates logs. Log rotation simply means to rename an existing log file to something else, thereby keeping the log file sizes tenable. Logrotate makes it easy to define log rotation rules, such as how many old logs to keep and for how long, the size a log should be before it's rotated, any post-rotation commands it needs to run, and more. | ||
== Introduction == | ==Introduction== | ||
Logrotate is typically found in your distro's repos as 'logrotate'. | Logrotate is typically found in your distro's repos as 'logrotate'. | ||
{{Highlight | {{Highlight | ||
| Line 8: | Line 8: | ||
| lang = terminal | | lang = terminal | ||
}} | }} | ||
Logrotate is triggered daily via a cronjob installed in <code>/etc/cron.daily/</code> | Logrotate is triggered daily via a cronjob and as a result, there is no logrotate daemon. Typically, the cronjob is installed in <code>/etc/cron.daily/</code> but could also be as a <code>@daily</code> job in <code>/etc/crontab</code> on some systems. | ||
By default, installing Logrotate will also include some standard configuration files that will rotate some common system logs in <code>/var/log</code>. | By default, installing Logrotate will also include some standard configuration files that will rotate some common system logs in <code>/var/log</code>. | ||
=== Configuration === | ===Configuration=== | ||
Configuration is done with <code>/etc/logrotate.conf</code> and additional log rotate definitions can be placed in <code>/etc/logrotate.d/</code>. For example, we could put httpd log rotation rules in <code>/etc/logrotate.d/httpd</code>. | Configuration is done with <code>/etc/logrotate.conf</code> and additional log rotate definitions can be placed in <code>/etc/logrotate.d/</code>. For example, we could put httpd log rotation rules in <code>/etc/logrotate.d/httpd</code>. | ||
| Line 80: | Line 80: | ||
<br /> | <br /> | ||
== Tasks == | ==Tasks== | ||
=== Rotating Traefik logs === | ===Rotating Traefik logs=== | ||
{{Highlight | {{Highlight | ||
| code = /var/log/traefik/*.log { | | code = /var/log/traefik/*.log { | ||
| Line 103: | Line 103: | ||
} | } | ||
| lang = text | | lang = text | ||
}} | }} | ||
Revision as of 23:56, 31 December 2021
Logrotate is a utility that rotates logs. Log rotation simply means to rename an existing log file to something else, thereby keeping the log file sizes tenable. Logrotate makes it easy to define log rotation rules, such as how many old logs to keep and for how long, the size a log should be before it's rotated, any post-rotation commands it needs to run, and more.
Introduction
Logrotate is typically found in your distro's repos as 'logrotate'.
# yum -y install logrotate
Logrotate is triggered daily via a cronjob and as a result, there is no logrotate daemon. Typically, the cronjob is installed in /etc/cron.daily/ but could also be as a @daily job in /etc/crontab on some systems.
By default, installing Logrotate will also include some standard configuration files that will rotate some common system logs in /var/log.
Configuration
Configuration is done with /etc/logrotate.conf and additional log rotate definitions can be placed in /etc/logrotate.d/. For example, we could put httpd log rotation rules in /etc/logrotate.d/httpd.
Log rotations are defined with the following syntax:
/path/to/logs/*.log {
** Directives **
}
It should also have at minimum the following directives:
| What | Directives |
|---|---|
| When to rotate. By time or by size. | daily, weekly, monthly
OR size based:
|
| How many rotated logs to keep. Eg. keep 30 logs. Anything past this will be deleted.
Set this to 0 to delete all rotated logs. |
rotate 30
|
You may also optionally add the following directives depending on your needs:
| Whether to create a new empty log | create, nocreate
|
| Use date as the suffix for rotated logs using the specified date format.
Creates logs like 'messages-2020-12-26' |
dateext
|
| If you are not using date extensions, logrotate will use numbers starting at 0 instead.
Specify the starting number. Eg. 1. The first rotated log would be ' |
start 1
|
| Whether to compress the log or not. Uses gzip by default. | compress
|
| The extension of rotated log files. Eg. 'messages-2020-12-26.log' or 'messages.0.log'. | extension log
|
| Send an email when a log is rotated out of existance. | mail user@domain.com
|
| Ignore if file is missing | missingok
|
| Don't rotate if the file is empty | notifempty
|
| Run a command after the rotation is executed.
The contents are run using |
postrotate
/bin/kill -HUP
endscript
|
Tasks
Rotating Traefik logs
/var/log/traefik/*.log {
daily
rotate 30
missingok
notifempty
compress
dateext
dateformat .%Y-%m-%d
create 0644 root root
size 10M
rotate 50
missingok
notifempty
postrotate
docker kill --signal="USR1" $(docker ps | grep traefik | awk '{print $1}')
endscript
}