-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vulnerability Detector module is enabled at the start of the stress test #22565
Labels
Comments
This was referenced Mar 15, 2024
MARCOSD4
changed the title
Vulnerability Detector module is enabled during stress test
Vulnerability Detector module is enabled at the start of the stress test
Mar 15, 2024
This was referenced Mar 15, 2024
This was referenced Mar 18, 2024
This was referenced Mar 19, 2024
From This fix will affect the stress test results, we should consider moving it to 4.9.0 instead of 4.8.2 |
This was referenced Jun 3, 2024
This was referenced Jun 10, 2024
This was referenced Jun 10, 2024
This was referenced Jun 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
During the testing in Release 4.8.0 - Beta 4 - Footprint Metrics - ALL (2.5d) some warnings related to the vulnerability scanner module have been encountered. After checking the configuration, the vulnerability detection module is disabled but in manager logs we see this module is enabled for a few minutes:
This happens because at the beginning of the test, it is taking a default Wazuh configuration from a template, which is producing these logs and warnings at the start of the test.
It significantly impacts the results of the stress tests.
The text was updated successfully, but these errors were encountered: