We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
During the testing of Release 4.10.0 - RC 3 - Vulnerability Detection performance test, it has been found that some components from worker 2 have stopped working in the middle of the test, like the following image:
This behavior has been seen in all the plots from Worker 2
The tests have been launched with the CLUSTER-Workload_benchmarks_metrics pipeline, using the following environment:
Build: https://ci.wazuh.info/job/CLUSTER-Workload_benchmarks_metrics/838/
Build 838
The text was updated successfully, but these errors were encountered:
Probably related to the unexpected error reported in #27546
Sorry, something went wrong.
Exactly @Rebits I explain it here #27546 It is likely that the script stopped writing from then on, because it was operating wazuh.
Closed in favor of what is explained here:
#27546 (comment)
Dwordcito
No branches or pull requests
Description
During the testing of Release 4.10.0 - RC 3 - Vulnerability Detection performance test, it has been found that some components from worker 2 have stopped working in the middle of the test, like the following image:
This behavior has been seen in all the plots from Worker 2
Environment
The tests have been launched with the CLUSTER-Workload_benchmarks_metrics pipeline, using the following environment:
Build: https://ci.wazuh.info/job/CLUSTER-Workload_benchmarks_metrics/838/
Build parameters
Build 838
Evidences
The text was updated successfully, but these errors were encountered: