Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] | Develop specific Wazuh agent for MacOS M1 chips #15055

Closed
j0serca opened this issue Sep 30, 2022 · 6 comments
Closed

[Feature Request] | Develop specific Wazuh agent for MacOS M1 chips #15055

j0serca opened this issue Sep 30, 2022 · 6 comments

Comments

@j0serca
Copy link
Member

j0serca commented Sep 30, 2022

Wazuh version Component Install type Install method Platform
4.x Wazuh agent Agent Packages/Sources macOS

Hi team,
Wazuh-agent package is natively built for Intel and uses translation to support Apple silicon (M1) processors, and it consumes an outstanding amount of CPU.

image

So my request would be to consider developing a specific wazuh-agent package that natively supports macOS M1 chips, for enhanced performance.

Thank you!

@alberpilot
Copy link
Contributor

alberpilot commented Feb 9, 2023

This request requires multiple team collaboration:

  • It's necessary to be able to compile the agent in the mentioned architecture.
  • It's needed to create a specific installer for this architecture.
  • Additionally, it will be necessary to check that syscollector retrieve correct data about the system. This check should be done from the Wazuh dashboard.
  • It's necessary to include the new installers in the CICD building and release processes.
  • The Wazuh dashboard plugin should be modified when deploying agents allowing the architecture selection.
  • Finally, documentation should be modified accordingly.

Tasks

@alberpilot alberpilot added the epic label Feb 9, 2023
@teddytpc1 teddytpc1 added type/enhancement New feature or request level/epic labels Apr 21, 2023
@havidarou havidarou moved this to Blocked in Release 4.4.3 May 19, 2023
@havidarou havidarou moved this to Blocked in Release 4.4.3 May 19, 2023
@wazuhci wazuhci moved this to Blocked in Release 4.4.4 May 23, 2023
@davidjiglesias davidjiglesias moved this from Blocked to In progress in Release 4.4.4 May 25, 2023
@wazuhci wazuhci moved this from In progress to Blocked in Release 4.4.4 May 25, 2023
@wazuhci wazuhci moved this to Blocked in Release 4.4.5 Jun 2, 2023
@y0d4a
Copy link

y0d4a commented Jun 4, 2023

Hi, any update on this?

@vikman90
Copy link
Member

@y0d4a We're currently working on this task, and we expect to release it in the next version (4.4.5).

Best.

@y0d4a
Copy link

y0d4a commented Jun 15, 2023

Fantastic!! you guys are amazing ! thank you!

@wazuhci wazuhci moved this to Blocked in Release 4.5.1 Jun 26, 2023
@wazuhci wazuhci removed this from Release 4.4.5 Jun 26, 2023
@wazuhci wazuhci moved this from Blocked to In progress in Release 4.5.1 Jul 27, 2023
@ghost
Copy link

ghost commented Aug 3, 2023

One question, will it arrive soon ?

@davidjiglesias
Copy link
Member

@BirdInFire Yes, it will

@vikman90 vikman90 closed this as completed Aug 4, 2023
@wazuhci wazuhci moved this from In progress to Done in Release 4.5.1 Aug 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Status: Done
Development

No branches or pull requests

7 participants