Websocket communication

[eva672]

Description

Replace the current TCP polling mechanism with WebSocket communication in wazuh-agent-status.
The goal is to establish a persistent connection between the client and server so that the client receives real-time agent status updates without polling.

Key tasks:

• Add WebSocket server support in the background process (server binary).
• Update client to subscribe to server via WebSocket.

---

Definition of Ready

• Codebase is cloned and dependencies resolved.
• Current TCP polling implementation is understood.

---

Acceptance Criteria

• Client establishes persistent WebSocket connection to server.
• Server broadcasts agent status changes to all connected clients.
• Client updates tray icon / CLI immediately upon receiving status update.

---

Definition of Done

• WebSocket server implemented in server binary.
• Client binary consumes WebSocket messages instead of polling.
• Unit and integration tests created for WebSocket communication.
• Documentation updated (README, developer guide) with new WebSocket design and configuration (--use-websocket flag).
• Manual test verified: stopping/starting Wazuh agent triggers immediate tray client update without polling.

---

[ArmandMeppa]

Currently working on establishing websocket communication b/w the server and the client

[eva672]

Succeeded to establish a websocket connection b/w the client and the server

[eva672]

After establishing the connection btw the client and server these are the logs i was able to get

You can see on the image the client logs that was been sent by the server which displays 3 messages

• The status of the agent
• The version
• The update

[eva672]

Currently working on websocket memory usage

[eva672]

• Currently working on fixing the issue faced with the memory usage

[t-desmond]

Went through codebase, working on understanding @eva672 websocket implementation