[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#921351: [pkg-go] Bug#921351: prometheus-postfix-exporter: Init script missing



Hi Martin et al,

A bit of a late reply here - there is a new version of postfix_exporter upstream, which finally implements log tailing. This would negate the need to fiddle with syslog config and use separate log file (which the exporter previously truncated).

Here is the relevant pull: https://github.com/kumina/postfix_exporter/pull/17

The exporter would just need to have sufficient group membership (e.g. adm) to be able to read e.g. /var/log/mail.log.

Cheers

On 11.02.19 12:56, Martín Ferrari wrote:
On 11/02/2019 11:32, Daniel Swarbrick wrote:
Hi Martin,

On 11.02.19 12:21, Martín Ferrari wrote:
Yes, I realised that when I was working on the package. But this does
not solve the issue about supporting sysv, so I added a rsyslog snippet
to create the separate logfile, and removed the systemd.enable flag from
the default so both versions use that logfile.
Is there any way the exporter could use the systemd journal when in a
system environment, and only fall back to using the extra log file when
running under sysv?
It could by just passing the option in the service file, but I did not
find a way to enable the separate log file only when under sysv, so it
would end up accumulating used disk space if using systemd and thought
that would be worse.


--
Daniel Swarbrick
Senior Systems Developer

1&1 IONOS Cloud GmbH | Greifswalder Str. 207 | 10405 Berlin | Germany
Phone: +49 30 57700-8299 | Fax: +49 30 57700-8598
E-mail: daniel.swarbrick@cloud.ionos.com | Web: www.ionos.de

Head Office: Berlin, Germany
District Court Berlin Charlottenburg, Registration number: HRB 125506 B
Executive Management: Christoph Steffens, Matthias Steinberg, Achim Weiss

Member of United Internet

This e-mail may contain confidential and/or privileged information. If you are
not the intended recipient of this e-mail, you are hereby notified that saving,
distribution or use of the content of this e-mail in any way is prohibited. If
you have received this e-mail in error, please notify the sender and delete the
e-mail.


Reply to: