Re: [Users] VSDM´s logrotate makes Hosts fill up var eventually
On Jan 9, 2014, at 10:33 AM, Dan Kenigsberg <danken(a)redhat.com> wrote:
The question of how much logging we should keep is a tough one. I, as
a
developer, would like to have as much as possible. For long-running busy
systems, it has happened to me that the core bug was spotted in
vdsm.log.67 or so.
However, I understand that verbosity has its price. To understand
whether we are stable enough to change the defaults, I need volunteers:
people who are willing to change their log level to INFO or WARNING, and
see if they miss useful information from their logs.
When you make you log level higher, you can lower the number of kept
log files, as they would not be filled as quick.
Would you, users@, help me with hard data?
I played with turning the verbosity down and keeping fewer logs, but in the end I wound up
adjusting the drive layout on my nodes (running centos with vdsdm added, not “pure” ovirt
nodes). If a VM crashes and leaves cores, I can run into problem, but monitoring alerts me
and I can take action.
It does seem a bit much though, maybe an easy switch in the GUI to allow setting it to
DEBUG when needed, and start off at WARNING for my production nodes? I think this feeling
is in part because it takes a bit of work me, an experienced power admin but not
developer, to dig stuff out of the logs myself, and most of it is not useful to me. So the
volume is a bit much. Of course, like all logs, they’re invaluable sometimes, and you
never know when you’ll need them, so…
-Darrell