Red Hat Bugzilla – Bug 1284432
[RFE] Provide a way to easily configure the log level for ovirt optimiser and optaplanner
Last modified: 2016-10-17 09:09:48 EDT
Description of problem:
It s currently not easy to adjust the log level for ovir optimiser and optaplanner. There needs to be way to do this easily. For example a configuration file in /etc/ovirt-optimizer/
Version-Release number of selected component (if applicable):
@Martin Sivak For OptaPlanner, adjusting the logging level is decribed here:
So I presume this will be a matter of bridging that to /etc/ovirt-optimizer somehow. If you're using logback as the logging implementation, the log level can be adjusted at runtime during bootstrap (see Logback/Slf4J documentation).
Since the ability to properly debug is important enough,
targeting for 3.6.4.
Uh Roman, what version did you test? You were running the 3.5 deployment when we were discussing this.
3.6 is very different in this area. It uses a proper ovirt-optimizer-jboss service and there is a config file in /usr/share/java/ovirt-optimizer/jboss7.war/WEB-INF/classes/log4j.properties
It might be a good idea to add a symlink to /etc/ though.
At that time the deployment was 3.5. The issue was noticed on a production system.
This bug is flagged for 3.6, yet the milestone is for 4.0 version, therefore the milestone has been reset.
Please set the correct milestone or add the flag.
Already merged, but I do not have the build version yet as there are more changes to come.
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see email@example.com with any questions
Can be move to MOD now?
Doron asked me to wait with downstream Optimizer update until we finish the RPMs of Optaplanner. So I do not have the downstream build yet.
verified on :
1. installing the optimizer
2. edit the last two lines in the file : /etc/ovirt-optimizer/jboss-log4j.properties
to the wanted behaviour: DEBUG/WARNING/INFO/ERROR
for example :
3. restart the ovirt-optimizer-jboss service
4. check that the logs are in the correct behaviour
( in : /var/log/ovirt-optimizer/jboss/ovirt-optimizer.log)