You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
jellyfin mpv shim is spamming in logs, which is especially noticeable when you launch it as daemon. That way, when you use journalctl, you get spammed by ping messages.
Right now, logging is hardcoded in log_utils.py by setting level for root_logger to DEBUG.
Describe the solution you'd like
There is mpv_log_level parameter already. Instead, log_level could be introduced, which can be applied to both mpv and shim itself. mpv_log_level can be either dropped or left to be used as additional parameter to override log levels for mpv.
Describe alternatives you've considered
Patching code myself
Writing logs to file (which are still verbose and take up space)
The text was updated successfully, but these errors were encountered:
Use mpv_log_level to set shim logger level too.
That should remove excessive chatter from pings to the server.
Set level to INFO by default. During normal operations people
don't need to have debug enabled.
Fixesjellyfin#372
Is your feature request related to a problem? Please describe.
jellyfin mpv shim is spamming in logs, which is especially noticeable when you launch it as daemon. That way, when you use journalctl, you get spammed by ping messages.
Right now, logging is hardcoded in
log_utils.py
by setting level forroot_logger
toDEBUG
.Describe the solution you'd like
There is
mpv_log_level
parameter already. Instead,log_level
could be introduced, which can be applied to bothmpv
and shim itself.mpv_log_level
can be either dropped or left to be used as additional parameter to override log levels formpv
.Describe alternatives you've considered
The text was updated successfully, but these errors were encountered: