Wazuh Dashboard first steps

[gdiazlo]

Wazuh dashboard

This repository forks the OpenSearch Dashboards repository to introduce changes that will ease its usage by Wazuh users and integrate itself with the Wazuh development process.

We want to accommodate our UX changes within the upstream code, minimizing conflicts. We want to contribute bug fixes and any component not tied to Wazuh upstream.

Also, we need to check all standard (vanilla) plugins are compatible with our builds, or we will need to build the infrastructure to build them ourselves too.

To do

Our release branch will be based on OpenSearch Dashboards 2.4.1 and upwards.

• Repository maintenance
  • Define the process to bring upstream changes #2
  • Replace README #43
  • Add branches from upstream #10
• Infrastructure / CI pipelines
  • Create docker-compose development environment #21
  • Build packages using GitHub Actions #11
  • Define build process
  • Research about the generation of OS packages (rpm, deb) #58
• Introduce Wazuh changes
  • Accommodate tests to pass #36
    • Modify unit tests #38
    • Skip/fix failing Cypress tests #34
  • Change CSS styles and images #15
  • Hide overview app and its links #37
  • Remove the tenant pop-up #16
  • Replace redirection to /home with /app/wazuh #17
  • Replace documentation links with Wazuh's #18
  • Disable the addition of sample data #19
  • Add ability to manage the Wazuh app using the plugin manager (bin/opensearch-plugins) #25
  • Create default config files for Wazuh #26
• Test the development cycle
  • Generate production packages with Wazuh changes and config files #46

[AlexRuiz7]

To keep this repository up-to-date with the original OpenSearch Repository, we need to periodically sync the fork bringing here (fork) the new changes made in the original repository (upstream).

For that, we'll follow the strategy defined in this article. To minimize the conflicts between the repos, we'll use the rebase strategy, replaying our work on top of OpenSearch Dashboards features.

We want to sync the fork once a week at least, so we'll also need to automatize this process. For that, we'll use GitHub Actions, and this action in particular.

[hieu-ht]

Hello Wazuh Team!
I want to ask whether the version of Wazuh dashboard at this docker image wazuh/wazuh-dashboard:4.3.11-dev is using code from this repo or using Kibana with plugin Wazuh-kibana-app?
Thanks!

[gdiazlo]

@hieu-ht it uses the code from wazuh-kibana-app and a standard binary distribution of opensearch. Our plan is to generate our own version of opensearch-dashboards from this repository in the coming weeks.

Initially, the changes we're going to introduce here are the ones we're applying to the standard distribution in our packaging pipeline.

[AlexRuiz7]

URL of the OpenSearch Security plugin: https://repo1.maven.org/maven2/org/opensearch/plugin/opensearch-security/2.4.1.0/opensearch-security-2.4.1.0.zip

[AlexRuiz7]

Merging order

Edit: we have accidentally merged pull requests using the merge commit option, blurring the git history. We also detected some commits that were not included by a pull request and are not signed. We are migrating all pull requests to a new branch named wz-init, branching off the 2.4.1 tag.

Branch	Pull request
34-fix-cypress-workflow	#49
38-modify-unit-tests	#48
43-replace-readme	#51
21-create-development-docker	#52
11-add-build-workflow	#42
26-add-default-config-files	#53
15-add-visual-changes	#50
37-hide-overview-app	#54
18-add-wazuh-metadata	#55
19-remove-sample-data	#56
25-manage-wazuh-plugin	#28