You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to run some integration tests, it is necessary to add lines to the local_internal_options.conf file to enable the ossec.log logging debugging for certain modules. Ideally, this configuration should be applied by the tests themselves (in fact, there are some that already do it), but in the meantime, it is necessary to add this configuration as a precondition to launch the test.
So far, qa-ctl is introducing the logging of all modules statically before running any test. This is inefficient and may even cause problems, since enabling logging of all modules may crash the FileMonitor and cause the test to fail causing a false positive.
As a last option, one could delegate such configuration to the environment provisioning, but this is still not efficient, since logging of all modules would have to be enabled.
It is requested to optimize this procedure so that only the minimum necessary lines are added for the test to work as long as they do not previously exist in that file. To do this, it is necessary to investigate the best way to do it, since this information can come from the test documentation, or have a dictionary that correlates the type of tests and configuration to be used.
The text was updated successfully, but these errors were encountered:
Hi,
In order to run some integration tests, it is necessary to add lines to the
local_internal_options.conf
file to enable theossec.log
logging debugging for certain modules. Ideally, this configuration should be applied by the tests themselves (in fact, there are some that already do it), but in the meantime, it is necessary to add this configuration as a precondition to launch the test.So far,
qa-ctl
is introducing the logging of all modules statically before running any test. This is inefficient and may even cause problems, since enabling logging of all modules may crash theFileMonitor
and cause the test to fail causing a false positive.As a last option, one could delegate such configuration to the environment provisioning, but this is still not efficient, since logging of all modules would have to be enabled.
It is requested to optimize this procedure so that only the minimum necessary lines are added for the test to work as long as they do not previously exist in that file. To do this, it is necessary to investigate the best way to do it, since this information can come from the test documentation, or have a dictionary that correlates the type of tests and configuration to be used.
The text was updated successfully, but these errors were encountered: