Wazuh at a glance
Is Wazuh OK?
One short question tells you whether the manager is healthy and whether your servers are still reporting to it.
What you get: the manager’s health, which daemons are stopped and whether that matters, and how many agents are active or disconnected, with the one problem worth acting on called out. Nothing on your servers changes.
Ask Quox
Section titled “Ask Quox”is wazuh ok
▤ AOCL │ L1 identity complete · allowed · 1ms
▤ AOCL │ L3 policy gate complete · proceed · 9ms
◐ QUOX │ cli ✔ QUOX │ cli │ 0 exit code, 8531 duration ms · 10.8s
⛓ AEE │ envelope opened · ops.tool · quox_cli ok
⛓ AEE │ envelope opened · stream_success
Wazuh is mostly fine. The manager reports healthy, and all the core daemons are running (analysisd, remoted, authd, logcollector, syscheckd, apid and the rest). • Stopped daemons: agentlessd, csyslogd, dbd, maild, reportd and clusterd. The tool lists no core daemons as stopped, so these are optional ones that aren't in use. That is normal for a single-node setup with no mail or cluster configured. • Agents: 3 enrolled, counting the manager. Only 1 is active and 2 are disconnected. Excluding the manager, that means both enrolled endpoints are disconnected. The disconnected agents are the real problem. While they're offline, Wazuh isn't collecting events from those hosts. The LUCID briefing also lists a medium finding for an sshd brute-force alert (rule 5712) on hyp-web-01. I haven't checked whether hyp-web-01 is one of the disconnected agents. I can ask argus to find which agents are disconnected and since when, and to check whether hyp-web-01 is among them. Shall I?
19.8s · 1 tool · 0 approvals
quox.✔ Machine verified against the CLI on 11 Nov 2026 · test report mwcj40
Quox read the manager status once and answered from it. The manager was healthy with every core daemon running; the six stopped daemons (mail, cluster, database output and the like) are optional ones a single-node setup does not use. It counted three agents including the manager, with both real endpoints disconnected, and named that as the problem: while they are offline, Wazuh collects nothing from those hosts. It also passed on an open brute-force finding for hyp-web-01, said plainly that it had not checked whether that host was one of the disconnected ones, and offered to have ARGUS, the Wazuh specialist, find out rather than guessing.
Do it yourself
Section titled “Do it yourself”1. Check the manager
Section titled “1. Check the manager”quox wazuh statusⓆ QUOX │ wazuh status │ manager healthy · 3 agents ✔Manager healthy: 11 running, 6 stoppedwazuh-agentlessd stopped (optional)wazuh-clusterd stopped (optional)wazuh-csyslogd stopped (optional)wazuh-dbd stopped (optional)wazuh-maild stopped (optional)wazuh-reportd stopped (optional)Agents: 2 active · 1 disconnected3 agents (incl. the manager, agent 000); 2 agents excluding it, as quox wazuh coverage counts. Bare quox wazuh runs the same check. It exits 3 when the manager is unhealthy, so a script or a cron job can act on it.
2. See which agents are disconnected
Section titled “2. See which agents are disconnected”quox wazuh agentsⓆ QUOX │ wazuh agents │ 3 agents ✔ID NAME IP STATUS OS VERSION LAST SEEN000 hyp-wazuh-01 127.0.0.1 active Ubuntu v4.12.0 manager (local)001 hyp-web-01 192.0.2.22 disconnected Ubuntu v4.12.0 5h 52m ago002 hyp-db-01 192.0.2.21 active Ubuntu v4.12.0 9s ago By the time we ran these commands hyp-db-01 had reconnected, so the CLI shows one disconnected agent where the conversation saw two. hyp-web-01, the host with the brute-force finding, was still offline.
What just happened
Section titled “What just happened”Quox read the Wazuh manager’s status. Reading changes nothing, so no approval was needed. Anything that would change a server, such as deploying or removing an agent, waits for a person to approve it.