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

[Ingest Manager] Support for multiple kibana urls #75710

Closed

Conversation

neptunian
Copy link
Contributor

#72731

Changes

  • the kibana configuration xpack.ingestManager.fleet.kibana.host now accepts both a string url or an array of string urls.
  • the Kibana URL in the settings flyout is now a EUI combo box that allows for multiple URLS

Screen Shot 2020-08-21 at 6 11 22 PM

  • the ingest_manager_settings saved object's kibana_url attribute is now an array of strings type
  • the PUT /api/ingest_manager/settings was changed from allowing only a string url to allowing only an array of string urls. GET always returns kibana_url as an array of strings.

TODO / Questions

  • validate yaml input and UI so only the hostname can differ in the urls
  • can the elastic agent cli be modified to accept a comma separated list of hosts? Currently the array of urls is being passed through and shown in the command for the user. Otherwise we can just pick the first or random url from the array.

Screen Shot 2020-08-21 at 6 11 33 PM

- if the user updates the urls, the agent doesn't know? (I think I understood this from @nchaulet)

@neptunian neptunian self-assigned this Aug 21, 2020
@neptunian neptunian force-pushed the 72731-allow-multiple-kibana-hosts branch from c515d07 to abc8028 Compare August 21, 2020 22:26
@neptunian
Copy link
Contributor Author

closed for #75712

@neptunian neptunian closed this Aug 21, 2020
@kibanamachine
Copy link
Contributor

💚 Build Succeeded

Build metrics

async chunks size

id value diff baseline
ingestManager 1.1MB +197.0B 1.1MB

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

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

Successfully merging this pull request may close these issues.

2 participants