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

Docker Dashboard missing indexer url variable #1194

Closed
wuast94 opened this issue Jan 22, 2024 · 1 comment
Closed

Docker Dashboard missing indexer url variable #1194

wuast94 opened this issue Jan 22, 2024 · 1 comment
Assignees

Comments

@wuast94
Copy link

wuast94 commented Jan 22, 2024

Ah sorry, I understand now, yes, you are right, if the wazuh-manager uses the INDEXER_URL in the environment section, the wazuh-dashboard should specify it too, please open an issue about this as it could need internal code changes

as discussed in #1191 the dasboard container missing an Envirement variable to set the indexer url. the indexer url is hardcoded in the container.

the master container has this option

@vcerenu vcerenu self-assigned this Mar 18, 2024
@vcerenu
Copy link
Member

vcerenu commented Mar 18, 2024

Hello @wuast94

I was reading the previous issue but what is not clear is that the use of the INDEXER_URL variable would be to replace the opensearch.hosts: value within the opensearch_dashboards.yml file so that it can be parameterized within the container.

The value is currently received when the config/wazuh_dashboard/opensearch_dashboards.yml file is mounted to the Wazuh dashboard container:

volumes:
  ...
  - ./config/wazuh_dashboard/opensearch_dashboards.yml:/usr/share/wazuh-dashboard/config/opensearch_dashboards.yml

If you want to configure this value you should modify it within this file.

We know that it is better to have parameters for each value, but for this we should carry out a development on the Wazuh dashboard image that we do not have contemplated within our current roadmap.

If you want to contribute your development on this topic, you are welcome, you can send us your PR and we will analyze it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants