[Pkg-matrix-maintainers] Bug#949103: default log level is too low

[Linda Lapinlampi]

control: tags -1 + moreinfo + confirmed

I'll summarize what was discussed in #matrix-debian:matrix.org so far.

This was the original bug: https://bugs.debian.org/927057

andrewsh@ argued (suggested) OP hadn't suggested an acceptable
configuration, which wouldn't reintroduce #927057 as an issue again.
Quote:

> The defaults should provide sane settings for a majority of users, but
> the synapse's defaults don't, they're good for those who want or have
> to tinker with the setup

> You can't just leave synapse running with those logging settings and
> forget about it

> so as I said, if we want to come to a mutually useful solution, could
> you please give me a combination of logging levels that doesn’t fill
> up the disk space with useless debugging _but_ provides useful data
> for you

I and another user suggested logging "desperately needs love" at
upstream, so considerably this is an upstream issue as well with
everything (debug information) being logged at INFO level with high IO
and disk space requirements.

OP argues:

> "turn everything off" is not considered useful

> Please please please reconsider the default logging level, or at least
> do your best to help users increase the logging before they come to us
> for support.

We (in the Matrix room) all seem to understand OP's frustration with the
inability to support Debian package users out of the box or decreased
user experience of "Debian is doing things differently". (Re: "do your
best to help users increase the logging before they come to us", I still
believe this is fundamentally an upstream issue to resolve too.)

A brief suggestion came up to ship a Debian package with two different
logging configurations. (I'm personally against this idea, for the sake
of maintaining simplicity.)

There were also some arguments about some WARNING and ERROR messages not
being useful (debug-like information). (Some of these were already
fixed upstream some releases ago.)

andrewsh@ said to collect some data to decide better about the
appropriate logging levels, and what changes might be required upstream.