Stabilize dashboard filtering test

[flash1293]

Fixes #55770

I could reproduce the problem of the original issue when testing against a real cloud instance. It seems like we are hitting some kind of circuit breaker which causes the request to fail with 504, probably because we are issuing lots of requests at once.

│ERROR browser[SEVERE] https://488dc2b34ba04eac84a982640b5dc769.eastus2.staging.azure.foundit.no:9243/elasticsearch/logstash-*/_search?rest_total_hits_as_int=true&ignore_unavailable=true&ignore_throttled=true&preference=1579821531484 - Failed to load resource: the server responded with a status of 504 ()
[

This is the error of the proxy:

{   "error_message": "backend closed connection",   "type": "proxy" }

On a second request against the same index it seems like the timing is different, because I never experienced a failure after refreshing - probably because some requests are already cached. Maybe this happens because the Kibana instance is underprovisioned in terms of RAM.

[elasticmachine]

Pinging @elastic/kibana-app (Team:KibanaApp)

[flash1293]

@elasticmachine merge upstream

[flash1293]

@liza-mae could you review this one so we can check whether it stabilizes the test?

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: b39699a

History

• 💚 Build #28146 succeeded ea010c4

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[liza-mae]

@flash1293 I ran this 25 times and did not see any failures, so it looks good to me.

[liza-mae]

LGTM