[Pulp-dev] Making pulp logging more configurable

[Matthias Dellweg]

Hi,
my thoughts:
Using syslog facilities maybe with [0] should integrate nicely with systemd
logging, however i do not know how well they integrate with s6
(oci-images). So the easiest way might be to get the systemd-unit of all
services to redirect stdout and stderr to syslog.
Otherwise we probably need an option whether to log to syslog (for sys V /
systemd installations) or stdout (for foreground / container operations).
  Matthias

[0] https://docs.python.org/3/library/logging.handlers.html#sysloghandler

On Tue, May 18, 2021 at 5:56 PM Tanya Tereshchenko <ttereshc at redhat.com>
wrote:

> Hi,
>
> I'd like to bring to your attention a suggestion [0] (based on a BZ [1])
> to categorize Pulp logs differently and have an ability to write them to a
> different place.
> Different users might want to do it differently, so I read it as an ask to
> make logging more configurable.
>
> It might also be a good opportunity to take a look at how friendly our
> docs and configuration are with regards to logging in general.
> FWIW, I found only this note [2] in the docs which mentions django logging
> and defers to the django docs.
>
> Please share any thoughts, concerns or ideas directly on the issue [0].
>
> Thank you,
> Tanya
>
> [0] https://pulp.plan.io/issues/8773
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1961508
> [2] https://docs.pulpproject.org/pulpcore/settings.html#logging
> _______________________________________________
> Pulp-dev mailing list
> Pulp-dev at redhat.com
> https://listman.redhat.com/mailman/listinfo/pulp-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20210519/ed27dfcf/attachment.htm>