elastic / kibana

Your window into the Elastic Stack
https://www.elastic.co/products/kibana
Other
19.67k stars 8.23k forks source link

[APM] Request timed out error returns when requesting top traces having set the search period out of the boost window #200619

Open ablnk opened 4 days ago

ablnk commented 4 days ago

Description: GET /internal/apm/traces?<> and /internal/apm/traces/find?<> requests fail with status code 500 and returns "Request timed out" when requesting top traces having set the search period out of the boost window.

{
    "statusCode": 500,
    "error": "Internal Server Error",
    "message": "Request timed out",
}

Steps to reproduce: Case 1 - GET /internal/apm/traces?<> The issue is only reproducible only in an environment with search power 35.

  1. Go to Applications - Traces.
  2. Set the search period to last 30 days.

Case 2 - GET /internal/apm/traces/find?<> The issue is reproducible in environments with search power 35 and search power 45.

  1. Go to Applications - Traces - Explorer.
  2. Set the search period to last 30 days.

Expected behavior:

Top traces list is loaded.

chrisdistasio commented 3 days ago

I believe we've ruled out changing SP to 35 and are defaulting to a # of 45. @cachedout can you please confirm?

elasticmachine commented 3 days ago

Pinging @elastic/unified-observability (Team:Observability)

ablnk commented 3 days ago

@chrisdistasio it's true, however the case 2 is reproducible in the environment with search power 45.