Kibana fails to create metricbeat index pattern

Elastic Stack Kibana
1

I tried to create a metricbeat-* index pattern directly from Kibana, but it fails with the following error:

Error: Request Timeout
at http://10.99.21.222:15601/bundles/commons.bundle.js:1:315503
at step (http://10.99.21.222:15601/built_assets/dlls/vendors.bundle.dll.js:359:4015)
at Object.next (http://10.99.21.222:15601/built_assets/dlls/vendors.bundle.dll.js:359:3275)
at fulfilled (http://10.99.21.222:15601/built_assets/dlls/vendors.bundle.dll.js:359:2669)

I'm using Elastic 6.7.1. Any clue about what could be the problem?

Thanks.

2

I tried on a fresh environment to upload dashboard and index pattern using metricbeat setup feature, but I still get several errors:

  • If I try to open the index pattern management page in Kibana I get simply an empty page and the following error is traced in the console:
commons.bundle.js:1 
PUT http://10.99.21.222:15601/api/saved_objects/index-pattern/metricbeat-* 408 (Request Timeout)
  • If I try to open the Discover panel, I get an empty page, and the following errors are traced/displayed by Kibana:
Error: Request Timeout
    at http://10.99.21.222:15601/bundles/commons.bundle.js:1:315503
    at step (http://10.99.21.222:15601/built_assets/dlls/vendors.bundle.dll.js:359:4015)
    at Object.next (http://10.99.21.222:15601/built_assets/dlls/vendors.bundle.dll.js:359:3275)
    at fulfilled (http://10.99.21.222:15601/built_assets/dlls/vendors.bundle.dll.js:359:2669)

Failed to load resource: the server responded with a status of 408 (Request Timeout)
----
vendors.bundle.dll.js:316 
[Violation] 'setTimeout' handler took 62ms
  • Some panels in the dashboards fail to load due to "Request timeout".

Any idea?

Thanks.

3

I managed to make this work, but only with specific versions:

Elastic 6.5.3
Metricbeat: 6.7.0

It looks definitely like a bug in the Elasticsearch index templates...

4

Today I run some further tests and I opened Kibana from another PC (i.e. from a different Chrome instance) and also with all components on 6.7.1 it seems to work.
I also tried from MS Edge and it seems ok.

At this point I think it was some issue between Chrome and Kibana, resulting in a Timeout Request exception. I'd close this thread and wait to see if the same issue happens again.

Thanks

5

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.