Dashboard timeout but individual visualisation is fast

Elastic Stack Kibana
1

I have a dashboard which contains about 10+ visualisations. This dashboard always timeouts (default 30s) whenever I query last 24 hours' data. However, if I bring out each individual visualisation and query last 24 hours data, most of them are very fast, taking only 1-3 seconds, except 1 or 2 taking slightly longer, no timeouts.
I have no idea why this is happening, can someone help to explain? Thanks a lot!

I'm using Kibana 4.6

2

Hi @zpp,

A few follow up questions so we can start figuring out what's going on here:

  1. Are you seeing any errors in the Kibana server log? If so, could you please paste them here.

  2. Are you seeing any errors in the browser's developer console? If so, could you please paste them here.

  3. If you open your browser's developer tools, networking tab, you will see an _msearch request being made when you load the dashboard page. Could you paste the response of this request here please?

Thanks,

Shaunak

3

@shaunak, thanks for your reply, here are the information:

  1. I don't see errors in the Kibana server logs. Mostly log lines are something like below:
    {"type":"response","@timestamp":"2017-03-14T03:14:07Z","tags":[],"pid":56409,"method":"get","statusCode":304,"req":{"url":"/bundles/kibana.style.css?v=10146","method":"g
    {"type":"response","@timestamp":"2017-03-14T03:14:07Z","tags":[],"pid":56409,"method":"get","statusCode":304,"req":{"url":"/bundles/kibana.bundle.js?v=10146","method":"g
    {"type":"response","@timestamp":"2017-03-14T03:14:08Z","tags":[],"pid":56409,"method":"get","statusCode":200,"req":{"url":"/app/kibana","method":"get","headers":{"host":
    {"type":"response","@timestamp":"2017-03-14T03:14:10Z","tags":

  2. there are no errors in developer console, besides one "Could not locate that visualization". I've removed the visualization from dashboard.

  3. When there is timeout, there is no response for the _msearch. Response came back after we extended the timeout value in Kibana. 24 hours' data is about 6MB. I can't post the whole string here, do you have any particular string interested?

4

Thanks @zpp. Yeah, I was trying to determine where the bottleneck was. Sounds like its the _msearch request. Could you paste the body of this request (not its response) here? Maybe there are some clues there as to what's causing the slow down.

Thanks,

Shaunak

5

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