Hello Mumpfelpumf
The unattended installation that you share is done through a script and installs the set just by running it, the user who run it does not have to worry since the versions used are compatible.
The unattended installer automatically installs it without the need for the user to do anything, this is done in this order (just like the Step-by-Step procedure):
- Install Wazuh
- Install Elasticsearch
- Install Filebeat
- Install Kibana
The reason why Filebeat is installed after Elasticsearch is because Filebeat requires a connection with Elasticsearch, as can be seen in the last step of the installation by performing the "filebeat test output" command, which shows this result:
elasticsearch: https://127.0.0.1:9200...
parse url... OK
connection...
parse host... OK
dns lookup... OK
addresses: 127.0.0.1
dial up... OK
TLS...
security: server's certificate chain verification is enabled
handshake... OK
TLS version: TLSv1.3
dial up... OK
talk to server... OK
version: 7.10.2
On the other hand, in a distributed installation (I will refer to Step-by-Step), the Elasticsearch cluster is installed first, then the Wazuh cluster (where Filebeat is also installed) and finally the Kibana phase. This is intended to follow this order.
The problem of the user who opened the thread, was that in his installation he mixed different Filebeat packages causing an incompatibility as my colleague mentions. This, with the current guide, does not happen.
Do you have a problem running the unattended script? If so, could you tell us what it is?
Regards, Raul.