board_serial should really be part of the agent information and used as a unique agent ID

[fernandogont]

Description

Wazuh requires that the agent name is unique. This means that if you tray to install the Wazuh agent on two systems that have the same hsot name, without overriding the default hostname, installation will fail -- actually, the installation itself will succeed, but the second node reusing a name will not be able to register on the Wazuh server.

These is problematic in at least two scenarios:

• Some platforms -- notably MacOS usually employ default host names that will result in names collisions/repetition. So deploying Wazuh in these scenarios is problematic.

• There are also typically operational scenarios when e.g. a VM will be migrated to anew OS or platform version... so a new VM with the same name is created... and, at times, the new and the old vms (with the same name) will be operated during migration of one system to the other.

Recently (not sure when), you added the "board_serial" information to syscollector. It is superuseful to have this piece of information available. However, since the board_serial is not part of the core agent information -- and because you are not leveraging this piece of information -- the scenarios i've described above have not improved.

My suggestion is that you incorporate "board_serial" into the main agent information, and only require that board_serial is unique (or, at least, that the combination of board_serial and agent name are unique).

Tasks

The steps that have to be completed in order to close the issue.

• Add board_serial (currently in syscollector) to the main agent information
• Stop requiring that the host name is unique, and rather require that board_Serial is unique (or, that the combination of board_serial and agent name are unique).

Additional information