Nikolai!
Sorry for the late response.
I couldn't find any particular documentation for an offline upgrade, I'm thinking of 2 options
The first one would be downloading the respective package (wazuh manager) and installing it from the package itself (
here you will find the last versions of all of them).
The second one is using the same procedure you followed earlier, once 4.4 is released, all packages needed will be available to download, whether you do it directly or by the wazuh-install.sh script. If you do a little test, you will find out that the package administrator handles the version itself, it would upgrade it if you have an older version.
Regarding logs, guessing you have already checked that
wazuh is a SIEM itself (you could handle those logs internally avoiding any possible problem of interface with another app) but if that's not an option you could filter verbosity or enable/disable the different modules feeding the logs by modifying
local_internal_options.conf setting .debug to 0 - 2 according what you're looking for. Or changing the source where those logs are obtained by adding or removing <localfile>, <remote>, etc on
ossec.conf
As stated there, there's a pre-decoding phase where hostname and program_name are taken from part of the log header. and after that a Decoding phase where some extra info is obtained.
Having that in mind you will be able to see which agents are generating the logs (by hostname) and which programs also.
Windows log collection info:
https://documentation.wazuh.com/current/user-manual/capabilities/log-data-collection/how-to-collect-wlogs.html#how-to-collect-windows-logsIf there's no problem from your side can you answer me why are you trying or forced to use another SIEM alongside wazuh?
Hope that this answer suits you better, but please do not hesitate on any doubt.
Have a great day!