-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
setup.dashboards.always_kibana doesn't work with Kibana 5.6 #6090
Labels
Comments
+1 I am also having this issue with metricbeat
|
andrewkroh
added a commit
to andrewkroh/beats
that referenced
this issue
Jan 30, 2018
In order to handle the different Kibana /api/status response formats in 5.x and 6.x the client attempts to parse it as 6.x and then falls back to the 5.x format on error. However if it was successful at parsing it was a 5.x response type is still always reported that an error had occurred. Fixes elastic#6090
ruflin
pushed a commit
that referenced
this issue
Jan 31, 2018
In order to handle the different Kibana /api/status response formats in 5.x and 6.x the client attempts to parse it as 6.x and then falls back to the 5.x format on error. However if it was successful at parsing it was a 5.x response type is still always reported that an error had occurred. Fixes #6090
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Attempts to use
-E setup.dashboards.always_kibana=true
with Kibana 5.6 always result in an error. This is the code in question:beats/libbeat/setup/kibana/client.go
Lines 172 to 182 in 6130ef3
After it successfully falls back to unmarshaling with the 5.x data type the code path always hits line 181 which is to return an error like the one below.
The text was updated successfully, but these errors were encountered: