Cherry-pick #4867 to 6.0: Set default credentials for Kibana#4892
Merged
tsg merged 1 commit intoelastic:6.0from Aug 14, 2017
Merged
Cherry-pick #4867 to 6.0: Set default credentials for Kibana#4892tsg merged 1 commit intoelastic:6.0from
tsg merged 1 commit intoelastic:6.0from
Conversation
…e as for Elasticsearch (elastic#4867) - Raise an error in case there are no dashboards to be imported (cherry picked from commit fb3a7a3)
Contributor
|
jenkins, test it again |
leweafan
pushed a commit
to leweafan/beats
that referenced
this pull request
Apr 28, 2023
…e as for Elasticsearch (elastic#4867) (elastic#4892) - Raise an error in case there are no dashboards to be imported (cherry picked from commit a7b5064)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cherry-pick of PR #4867 to 6.0 branch. Original message:
When loading the dashboards from Beats 6.0, the user needs to configure:
In Could, the credentials for connecting to Elasticsearch are the same as for connecting to Kibana, so the last step can be removed if we take (by default) the Kibana credentials from the Elasticsearch credentials.
This PR gets by default the credentials for Kibana from Elasticsearch configuration.