public inbox for pmg-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: Dietmar Maurer <dietmar@proxmox.com>
Cc: pmg-devel@lists.proxmox.com
Subject: Re: [pmg-devel] [RFC pmg-log-tracker] do not assume constant year based on file index
Date: Mon, 3 Jan 2022 19:05:49 +0100	[thread overview]
Message-ID: <20220103190549.3fc8eae5@rosa.proxmox.com> (raw)
In-Reply-To: <1130358330.2251.1641231555805@webmail.proxmox.com>

On Mon, 3 Jan 2022 18:39:15 +0100 (CET)
Dietmar Maurer <dietmar@proxmox.com> wrote:

> > the old logic is flawed (but that can be said about parsing
> > traditional syslog timestamps (w/o year) in general) - it got worse
> > with the change in bullseye of rotating syslog weekly by default -
> > resulting in users losing one week of logs per day in the new year   
> 
> Daily syslog rotation is essential for high volume mail system. Else the log files gets far to big! 
> 
> So cant we simply change logfile rotation back to daily?

We can consider that - but for most bullseye installations the ship
has sailed (assuming that most users do not diff the configs when debian
asks them to and simply press 'keep my version')

Additionally the one year per log-file really seems brittle to me, or
rather the patch should be independent of the logrotation settings.

On the other hand - the volume of the logfiles does not bother me too much:
* since quite a long while /var/log/mail.log (in debian's standard
  logrotate config, which we do not touch) was always rotated weekly and
  contains all relevant logs for PMG (as an additional copy to what's
  already in /var/log/syslog) - and I think most users did not notice it
* users actually running high-volume sites quickly find out that they
  want/need to adapt their logrotation schedule 
* Finally I've seen a few posts in our support channels where users
  actively use weekly rotation and a keep of 32 to get more logs parsed
  and available in the GUI
* comparing the weekly logs of a fairly active site here (50k - 82k
  mails/month) - we get < 100 MB logs/week

My idea for the longer run would be to:
* add a dedicated log for pmg, which logs time in ISO8601 (or if this
  proves too expensive to pase in unix-timestamps) and maybe the hostname
* make retention configurable via GUI
* either suggest in a wiki-page/the reference documentation or actually by
  shipping a modified config file - to drop /var/log/mail.log (and in the
  long run maybe also the mail facility logging from /var/log/syslog)





  reply	other threads:[~2022-01-03 18:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-03 17:39 Dietmar Maurer
2022-01-03 18:05 ` Stoiko Ivanov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-01-03 16:23 Stoiko Ivanov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220103190549.3fc8eae5@rosa.proxmox.com \
    --to=s.ivanov@proxmox.com \
    --cc=dietmar@proxmox.com \
    --cc=pmg-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal