Hi,
and thanks for pointing this out.
Maybe my BZ at:
https://bugzilla.redhat.com/show_bug.cgi?id=1078738
could suffice as a first subtask in solving this issue by introducing
a syslog handler module shipped by ovirt for jboss 7.1
and maybe additionally put another couple of log4j.xml into
/etc/ovirt-engine/engine.conf[.d/*.conf] for the purpose of
logging.
the log4j.xmls are better to edit at least.
Am 20.03.2014 15:42, schrieb Alon Bar-Lev:
Hi,
The jboss service xml is sensitive monolithic block of data as any J2EE resource, to make
it complex, the format is XML.
We cannot put it in /etc as every upgrade requires to overwrite the file for product to
be usable.
In order to allow some level of customization we inject variable from
/etc/ovirt-engine/engine.conf[.d/*.conf] into the content upon service start. As the
logging part of this file, and the nature of the syntax is not fixed, I yet not found a
decent solution[1].
What I really want to see, is that we can programmatic control what loggers we have and
what level to enable and add these into our own configuration, detaching from jboss
configuration, and even maybe can modify the log level dynamically at runtime as expected
from this scale of application.
I had short discussion about this with Mooli, I hope someone is capable of taking such
task.
Regards,
Alon
[1]
https://bugzilla.redhat.com/show_bug.cgi?id=1017042
> >
--
Mit freundlichen Grüßen / Regards
Sven Kieske
Systemadministrator
Mittwald CM Service GmbH & Co. KG
Königsberger Straße 6
32339 Espelkamp
T: +49-5772-293-100
F: +49-5772-293-333
https://www.mittwald.de
Geschäftsführer: Robert Meyer
St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen
Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen