8:17 a.m.
Hi,
it's quite inconvenient that DEBUG messages are missing in OST Vdsm
logs. Would it be possible to enable them some way?
Thanks,
Milan
2:44 a.m.
On 04/12/2018 03:17 PM, Milan Zamazal wrote:
Hi,
it's quite inconvenient that DEBUG messages are missing in OST Vdsm
logs. Would it be possible to enable them some way?
Maybe just call vdsm-client once Vdsm is up? we can toggle the log
verbosiness at runtime.
I strongly support this idea - OST is probably one of the few places
outside developers' environments where DEBUG level by default fully
makes sense
However, I'd like to reminder that since the addition of the metadata.py
module, virt logs can be quite verbose. Raising this just because it could
eat some storage space on OST workers, so let's keep this item on the
watchlist.
--
Francesco Romani
Senior SW Eng., Virtualization R&D
Red Hat
IRC: fromani github: @fromanirh
8:36 a.m.
Francesco Romani <fromani(a)redhat.com> writes:
On 04/12/2018 03:17 PM, Milan Zamazal wrote:
> Hi,
>
> it's quite inconvenient that DEBUG messages are missing in OST Vdsm
> logs. Would it be possible to enable them some way?
Maybe just call vdsm-client once Vdsm is up? we can toggle the log
verbosiness at runtime.
A good idea since it doesn't require Vdsm restart. We just need to
track available loggers.
I strongly support this idea - OST is probably one of the few places
outside developers' environments where DEBUG level by default fully
makes sense
However, I'd like to reminder that since the addition of the metadata.py
module, virt logs can be quite verbose. Raising this just because it could
eat some storage space on OST workers, so let's keep this item on the
watchlist.
Hopefully not a big issue, we can discuss it in gerrit:
https://gerrit.ovirt.org/90262
Thanks,
Milan
2417
days inactive
2418
days old
2 comments
2 participants
participants (2)
-
Francesco Romani -
Milan Zamazal