On Tue, Apr 18, 2017 at 6:04 PM Greg Sheremeta <gshereme@redhat.com> wrote:
On Tue, Apr 18, 2017 at 7:40 AM, Martin Betak <mbetak@redhat.com> wrote:


On Tue, Apr 18, 2017 at 9:52 AM, Roy Golan <rgolan@redhat.com> wrote:
Ever wanted to raise level of the engine logs and wanted to to that fast and runtime?

This is a small wrapper around wildfly mgmt interface, called log-control to do the trick[1]

Example, debug the db interaction layer:

    ./log-control org.ovirt.engine.core.dal debug

It will first try blantly to add the log category and then will set the log level according to what you set. It is simple and stupid.

More interesting logger categories:

business logic (commands, queries) - org.ovirt.engine.core.bll
hosts interaction - org.ovirt.engine.core.vdsbroker
various utilities - org.ovirt.engine.core.utils
aaa - org.ovirt.engine.exttool.aaa

General suggestion -
I think is is it time for ovirt-engine-contrib so mini-helpers like that can exists and when they are solid can go into mainstream repo, if needed in there.

Nice job, Roy! +1 to the "ovirt-engine-contrib" idea.

+1 [aside -- suggest adding engine build aliases, git aliases, shell functions for building / maintaining multiple engine compilations and databases, etc.]


Exactly. Should it be a 'contrib' folder under the repo and then later we can create an rpm out of it if we want?

Btw VDSM has a contrib folder as well with interesting stuff (just stumbled upon profile-stats which I was completely unaware of)
 

_______________________________________________
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel


_______________________________________________
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel



--
Greg Sheremeta, MBA
Sr. Software Engineer
Red Hat, Inc.
gshereme@redhat.com