Wazuh | Mailing List

Hi, I will be responding to your questions. Regarding the actual issue: I went through the alert logs

I recently upgraded my server from 4.7 to 4.13 via a full reinstall & restore from backup, and

Hi Manuel, After changing this settings you still get an error when trying to create a new internal

Hi Gabriel, filebeat test output looks good, i think: filebeat test output elasticsearch: https://

Hi HAshita, I have multiple folders in path : C:\inetpub\logs\LogFiles Pe miercuri, 12 noiembrie 2025

Ok thanks Carlos, I'll check if i can find a workaround. I'll let you know. Br, Adrien Le

You have a timestamp in the log header Nov 12 08:00:23, which is not in the supported time format.

Hello Fernando, Could you clarify the S3 repository, please? Are you referring to https://www.elastic

Hello As the log is matching the program name in the pre-decoding phase, you need to use it in the

issue come back with wazuh-states-inventory-browser-extensions-* in 4.14.0 , as you can see below i

Hi Dhiren, Currently, there is no agent group field available for all wazuh-states-* indexes, and

Hi @Jaime Can you please check the ownership and permission of the file, the output should be: -rwxr-

Hi Nicolai, Sure, here are the command outputs. Its important to mention that I am currently using

Hi wazuh community, When I tried to change files by deleting or modifying them, there was an alert in

Hi Erick Quinto The Wazuh dashboard is not ready yet. This issue mainly happens when the wazuh-

We are currently using Wazuh Agent version 4.14, installed on SUSE Linux Enterprise Server 12 SP3.

Just to confirm, I believe you have already configured the archive.json (that is disabled by default)

Hi, now I see "No results match your search criteria. There are not Filters Il giorno mercoledì

Hello Bony I have checked the ossec.conf configuration file and the problem was with a new CDB list.

No worries!!! I am happy to help! enjoy Wazuh! On Tuesday, November 11, 2025 at 9:47:02 AM UTC-6

Hi thanks that has solved the issue with one client - but the other still showing the same issue On

Warhammerik, The problem is that the event header does not have a standard syslog format, so the pre-

Hi Tony, The reason alerts were not firing is that the monitor was configured to query both clusters

Hello Andrea, The problem is with the way you named your custom rule, this resonates with the naming

Hi, Handling over 2 million alerts over 12–13 hours (roughly 40–50 alerts/second) is pushing the

Hello, I reviewed your script and the rule logic and it looks fine. Your comparison uses “less than”

Hi I love Wazuh There is no Windows EventChannel XML decoder, as it is embedded inside Wazuh's

Hi Mani, This is not an expected behavior. This error seems to be related with an incomplete parsing

Hi, Apologies for the late response. By following the Mapping with Wazuh section in the Wazuh

Hello , i am currently getting following issue