Skip to content
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

Jobflow - Log should differentiate targets uniquely #5555

Open
rauldpm opened this issue Jul 9, 2024 · 0 comments
Open

Jobflow - Log should differentiate targets uniquely #5555

rauldpm opened this issue Jul 9, 2024 · 0 comments

Comments

@rauldpm
Copy link
Member

rauldpm commented Jul 9, 2024

Description

Testing the wazuh/wazuh#23748 issue it has been observed that the log file does not differentiate between the agents and the manager, as it uses the system and version to identify it

[2024-07-09 18:44:24,264] [INFO] TESTER: Checking connection to ubuntu-24.04
[2024-07-09 18:44:25,119] [INFO] TESTER: Connection established successfully in ubuntu-24.04
[2024-07-09 18:44:31,806] [INFO] TESTER: Uninstalling Agent in ubuntu-24.04

In the issue, a log file can be observed, which deploys three Ubuntu 24 systems (two agents ARM and AMD, one manager AMD)

Each line of the log must identify which target it belongs to (on which host the action is performed) if needed, for example:

[2024-07-09 18:44:24,264] [INFO] [ubuntu-24-amd-agent] TESTER: Checking connection to ubuntu-24.04
[2024-07-09 18:44:25,119] [INFO] [ubuntu-24-amd-manager] TESTER: Connection established successfully in ubuntu-24.04
[2024-07-09 18:44:31,806] [INFO] [ubuntu-24-arm-agent] TESTER: Uninstalling Agent in ubuntu-24.04
@rauldpm rauldpm changed the title DTT2 - Jobflow - Log should differentiate agents uniquely DTT2 - Jobflow - Log should differentiate targets uniquely Jul 9, 2024
@juliamagan juliamagan changed the title DTT2 - Jobflow - Log should differentiate targets uniquely Jobflow - Log should differentiate targets uniquely Aug 30, 2024
@wazuhci wazuhci moved this to Backlog in Release 5.0.0 Aug 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog
Development

No branches or pull requests

1 participant