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

Broken Metricbeat dashboards #4777

Closed
inqueue opened this issue Jul 27, 2017 · 5 comments · Fixed by elastic/kibana#13182
Closed

Broken Metricbeat dashboards #4777

inqueue opened this issue Jul 27, 2017 · 5 comments · Fixed by elastic/kibana#13182

Comments

@inqueue
Copy link
Member

inqueue commented Jul 27, 2017

Metricbeat 6.0.0-beta1 BC2

The Metricbeat host overview and Metricbeat system overview dashboards are showing error "The request for this panel failed." for several visualizations. The same visualizations load correctly when launched individually or placed in a new dashboard. The issue appears to be something specific to the dashboards.

Dashboards were installed with:

./metricbeat setup --dashboards

Host Overview

screen shot 2017-07-27 at 4 17 54 pm

System Overview

screen shot 2017-07-27 at 4 18 29 pm

Custom

screen shot 2017-07-27 at 4 10 35 pm

@exekias
Copy link
Contributor

exekias commented Jul 28, 2017

I've reproduced this issue

@exekias
Copy link
Contributor

exekias commented Jul 28, 2017

system dashboard 1

Graph seems to work while editing, it just fails in the dashboard, where I see this error message in the developer console

commons.bundle.js?v=15762:38 Error: [ngRepeat:dupes] Duplicates in a repeater are not allowed. Use 'track by' expression to specify unique keys. Repeater: legendData in labels track by legendData.label, Duplicate key: 100% - 100%, Duplicate value: {"label":"100% - 100%"}
http://errors.angularjs.org/1.4.7/ngRepeat/dupes?p0=legendData%20in%20label…el&p1=100%25%20-%20100%25&p2=%7B%22label%22%3A%22100%25%20-%20100%25%22%7D
    at commons.bundle.js?v=15762:35
    at commons.bundle.js?v=15762:43
    at Object.$watchCollectionAction [as fn] (commons.bundle.js?v=15762:39)
    at Scope.$digest (commons.bundle.js?v=15762:39)
    at Scope.$apply (commons.bundle.js?v=15762:39)
    at kibana.bundle.js?v=15762:126
    at complete (commons.bundle.js?v=15762:2)
    at delayed (commons.bundle.js?v=15762:2)

Still researching, this may be a kibana issue

@tsg
Copy link
Contributor

tsg commented Jul 28, 2017

Looks like this can be workedaround by simply entering the empty string (just press enter), or * in the search box.

@tsg
Copy link
Contributor

tsg commented Jul 28, 2017

I think what happened was that Kibana changed the format in which the query string is saved. This is in the imported dashboards:

{
  "filter": [
    {
      "query": {
        "query_string": {
          "analyze_wildcard": true,
          "query": "*"
        }
      }
    }
  ]
}

And this is how it looks in a newly created dashboard:

{
  "query": {
    "language": "lucene",
    "query": ""
  },
  "filter": [],
  "highlightAll": true,
  "version": true
}

@tsg
Copy link
Contributor

tsg commented Jul 28, 2017

Closing in favor of elastic/kibana#13181.

@tsg tsg closed this as completed Jul 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants