[courier] each dashboard panel search request getting sent in separate HTTP request

[nreese]

It looks like each panel is submitting its own _msearch HTTP request when fetching data instead of combining into a single _msearch request.

cc @stacey-gammon @spalger

[stacey-gammon]

Sometimes they are being grouped together. There is logic in there to send requests off every x ms, so sometimes, depending on how long it takes for one viz request to get added to the queue vs the next, they might go out in batches. It does seem to be splitting them up much more than previously though. I wonder if a timing thing changed...

[stacey-gammon]

I went back 10 days and am seeing the same kind of request separation.... will see what happens if I go back even further.

[stacey-gammon]

Went back 20 days, and same thing, so this is def not something recently introduced. I'll check a 6.2 version next to see how our released version is behaving.

[stacey-gammon]

v6.2 acts the same, so this isn't a blocker.

[spalger]

I'm also seeing multiple msearch requests (with three panels I get two requests sometimes), but only sometimes and only when initially loading the dashboard. In my network panel Chrome says that requests start at 5.48 and 5.5, which is greater than the default 10ms debounce time. Any idea when dashboard panels would have started loading async? AFAIK all panels are loaded by the saved object loader before any of them are rendered, but things have changed a lot since I was in there last.

[lukasolson]

Hmm, not seeing this behavior any more, and we're considering removing the batching behavior and replacing it with some other optimization (such as response streaming), so I'm going to close this.