Hello,
Thank you for using Wazuh!
In Wazuh, we have some pre-built stock decoders and rules for VMWare logs.
Decoders:
0360-vmware_decoders.xml Rules:
0235-vmware_rules.xml However, as your logs are coming properly to the archives.log of the manager, you can verify using
wazuh-logtest if the logs are being decoded and triggering alerts or not. You can learn more about wazuh-logtest here:
https://documentation.wazuh.com/current/user-manual/capabilities/wazuh-logtest/how-it-works.htmlIn the archives.log, the
"timestamp hostname path log" format. For example:
If the archives.log entry is:
2022 Nov 03 21:01:12 my-wazuh-server-01->1.2.3.4 1 2022-11-03T21:01:12.770471+00:00 my-vcenter-server-01 sps - - - 2022-11-03T21:01:12.770Z [pool-24-thread-1] INFO opId=sps-Main-495054-122 com.vmware.vslm.globalcache.GlobalCatalogCache - Total number of changes for sync-id: h0B49OZR2L is: 0
Your actual log to test in wazuh-logtest should be:
2022-11-03T21:01:12.770471+00:00 my-vcenter-server-01 sps - - - 2022-11-03T21:01:12.770Z [pool-24-thread-1] INFO opId=sps-Main-495054-122 com.vmware.vslm.globalcache.GlobalCatalogCache - Total number of changes for sync-id: h0B49OZR2L is: 0
If these logs are not being decoded or not triggering any rules, you need to create custom decoders and rules for them to generate alerts. You can review the following documents to learn more about custom rules and decoders.
I hope it helps. Please let us know how it goes.