Package: wnpp
Severity: wishlist
Owner: Antoine Le Gonidec <deb...@vv221.fr>
X-Debbugs-Cc: debian-de...@lists.debian.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

* Package name    : metalog
  Version         : 20230719
  Upstream Contact: Michael Kress <m-kr...@m-kress.de>
* URL             : https://metalog.sourceforge.net/
* License         : GPL-2
  Programming Lang: C
  Description     : A highly-configurable system logger

Metalog is a modern replacement for syslogd and klogd. The logged messages
can be dispatched according to their facility, urgency, program name and/or
Perl-compatible regular expressions. Log files can be automatically rotated
when they exceed a certain size or age. External shell scripts (e.g., mail)
can be launched when specific patterns are found.

Metalog is simple to configure, accepts unlimited number of rules and has
(switchable) memory bufferization for maximal performance.

- ---

With rsyslog pivoting to AI-based development, the main alternatives in
Debian are:
- - inetutils-syslogd
- - syslog-ng
(cf. https://bugs.debian.org/1109121 for rsyslog context)

Both have limitations: inetutils-syslogd does not allow splitting logs
in dedicated files using anything but the logs facility and priority,
and while syslog-ng is much more configurable it comes at the cost of a
syntax much harder to learn and an overwhelming upstream documentation.

Metalog seems to be much easier to configure, and should fit the needs of
a lot of system administrators who would find inetutils-syslogd too
limited, but syslog-ng far too big and twisted. It would perfectly fit
the niche left vacant by rsyslog.

While I plan on handling the initial packaging by myself, I would love
welcoming co-maintainers for this package. We do not seem to have a team
for the maintenance of logging daemons, otherwise I would have suggested
maintaining this package under such a team. Maybe it could be a good
opportunity to actually start that team?

I am not a Debian Developer yet so I might need a sponsor, but my
application process has already been mostly validated so that might no
longer be required by the time I have a first version of the package
ready to be uploaded to unstable.

-----BEGIN PGP SIGNATURE-----

iIYEARYKAC4WIQSUsdxM90hewW6X7Jhja3j5HOuA2AUCaHJ01xAcZGViaWFuQHZ2
MjIxLmZyAAoJEGNrePkc64DYkRIBAO4nBqCdEqCJsPLboaJ9qRV3ZMB2R7aUGXsU
8TwWHBQaAP963ncZRKcJISNEiNBx/a16fhQxOPg7UNJsDroBucvPDQ==
=ZrqW
-----END PGP SIGNATURE-----

Reply via email to