Update user used by Kibana
in the cluster performance tests
#1822
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR closes #1799.
Right now, we are using the APISimulator to simulate 2 different sources in our cluster performance tests:
The related issue aims to change the user used in the API simulated to
wazuh-wui
when we simulate the API using the Kibana APP. Therefore, logs from Kibana requests and Kibana requests with extra load will indicate the userwazuh-wui
instead ofwazuh
.The API logs generated by the API tests will still have the
wazuh
user.To do this, I have changed the default user and password used in the
APISimulator
class towazuh-wui
, as this class is only used to simulate the API when it is used by Kibana.Actual logs:
After the changes: