First, you can find the architecture specifications in the documentation here:
https://documentation.wazuh.com/current/quickstart.htmlGenerally speaking, it is less about the number of agents and more about how much they are actually sending—so EPS (events per second) and how long you keep the data matters the most.
EPS affects CPU and RAM (how much processing is needed)
Retention affects disk (how much data you are storing over time)
Wazuh does not really have a fixed "max EPS per node." It mostly comes down to the hardware and how much load it can handle.
As a starting point for 1000 agents
Wazuh manager: around 8 CPU cores, 16 GB RAM
Wazuh indexer: around 16 CPU cores, 32 GB RAM
For the disk, this depends entirely on your retention (30, 60, 90 days, etc.) and how noisy your environment is. Typically you can start with 1-2 TB and observe as it grows.
You need to keep an eye on the files below to be sure when you are hitting limits:
/var/ossec/var/run/wazuh-analysisd.state - (the variable events_dropped indicates whether events are being dropped due to a lack of resources.)
/var/ossec/var/run/wazuh-remoted.state - (the variable discarded_count indicates if messages from the agents were discarded.)
Ref:
Reference:
https://documentation.wazuh.com/current/user-manual/reference/statistics-files/index.htmlAdditionally, as Wazuh easily scales horizontally rather than vertically, we recommend adding a new node when you see drops in the events (taking into consideration the hardware specifications mentioned above).
So like I said, start with a decent baseline, then observe your EPS and dropped events, and grow from there.
Reference for EPS calculation:
https://blog.secopsgarage.com/eps_wazuh/