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

Metricbeat dashboards do not import correctly #2208

Closed
aleph-zero opened this issue Aug 9, 2016 · 11 comments
Closed

Metricbeat dashboards do not import correctly #2208

aleph-zero opened this issue Aug 9, 2016 · 11 comments

Comments

@aleph-zero
Copy link

On alpha5, when loading the dashboards from the import_dashboards.sh script, they do not show up in Kibana.

For confirmed bugs, please report:

  • Version:
    Alpha5
  • Operating System:
    OSX
  • Steps to Reproduce:
  • cd metricbeat-5.0.0-alpha5-darwin-x86_64/kibana && ./import_dashboards.sh
  • go to Kibana, try to Open a dashboard. There are none.
@tsg
Copy link
Contributor

tsg commented Aug 9, 2016

Related ES ticket: elastic/elasticsearch#19893

@monicasarbu monicasarbu added bug and removed Metricbeat Metricbeat labels Aug 9, 2016
@monicasarbu
Copy link
Contributor

Removing Metricbeat label, as the same error appears when loading any dashboard/index pattern.

@tsg
Copy link
Contributor

tsg commented Aug 10, 2016

A simple workaround is to replace one line in the import_dashboards.sh script, like this:

diff --git a/dev-tools/import_dashboards.sh b/dev-tools/import_dashboards.sh
index 231c97e..f5c5466 100755
--- a/dev-tools/import_dashboards.sh
+++ b/dev-tools/import_dashboards.sh
@@ -8,7 +8,7 @@

 # The default value of the variable. Initialize your own variables here
 ELASTICSEARCH=http://localhost:9200
-CURL=curl
+CURL="curl -H Expect:"
 KIBANA_INDEX=".kibana"
 DIR=.
 BEAT_CONFIG=".beatconfig"

tsg pushed a commit to tsg/beats that referenced this issue Aug 10, 2016
Workaround for elastic#2208. Elasticsearch alpha5 doesn't like the "Expect: 100-continue"
header that is added by curl. We should remove this workaround after the next
release is out.
ruflin pushed a commit that referenced this issue Aug 10, 2016
Workaround for #2208. Elasticsearch alpha5 doesn't like the "Expect: 100-continue"
header that is added by curl. We should remove this workaround after the next
release is out.
@tsg
Copy link
Contributor

tsg commented Aug 10, 2016

@dedemorton Do you think we could document this workaround in the getting started for the alpha5, similar to how we had a workaround for alpha4? I can then also add a notice to the blog post.

tsg pushed a commit to tsg/beats that referenced this issue Aug 10, 2016
This is a proposal documentation of the workaround for elastic#2208.
@tsg
Copy link
Contributor

tsg commented Aug 10, 2016

I made a proposal for the docs in #2218.

dedemorton pushed a commit that referenced this issue Aug 10, 2016
This is a proposal documentation of the workaround for #2208.
@tsg
Copy link
Contributor

tsg commented Aug 11, 2016

Closing this one as the workaround is in place in master and it's documented in the alpha5 docs. The Elasticsearch fix elastic/elasticsearch#19904 is also merged.

@tsg tsg closed this as completed Aug 11, 2016
@cwurm
Copy link
Contributor

cwurm commented Aug 15, 2016

Hm, the workaround doesn't work for me if I run the script with -u username:password.

@ruflin
Copy link
Member

ruflin commented Aug 16, 2016

@cwurm We missed that in case of -u CURL variable is overwritten locally: https://github.com/tsg/beats/blob/179e8770c6e0843e84a092a12706fdc70a002f19/dev-tools/import_dashboards.sh#L75 I'm going to reopen this issue.

@ruflin ruflin reopened this Aug 16, 2016
@monicasarbu
Copy link
Contributor

@cwurm can you please try to change this line:

 CURL="curl --user ${USER}"

with:

CURL="${CURL} --user ${USER}"

@cwurm
Copy link
Contributor

cwurm commented Aug 16, 2016

@monicasarbu That did it, works now.

@monicasarbu
Copy link
Contributor

This should be solved in 5.0.0-beta1, as we re-wrote the import script in Golang. #2155

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

5 participants