[inspector] show request method, path, and querystring

[nreese]

Closes #45931

PR updates data plugin search and bsearch endpoints to return method, path, and querystring request params from elasticsearch-js client requests. This provides inspector with the exact details used to fetch data from elasticsearch, ensuring inspector displays request exactly as used by elasticsearch-js client.

ESQL This PR makes it possible to open ESQL searches in console.

background

If you are thinking to yourself, "haven't I reviewed this before?", you are right. This functionality has been through several iterations.

1. Original PR [inspector] show request method, path, and querystring #166565 was reverted for exposing headers.
2. Fix to only expose method, path, and querystring keys from request parameters was rejected because it applied changes to kibana_utils/server/report_server_error.ts, which is used extensively throughout Kibana.
3. This iteration moves logic into the data plugin to be as narrow as possible.

[nreese]

@elasticmachine merge upstream

[elasticmachine]

Pinging @elastic/kibana-presentation (Team:Presentation)

[dej611]

Tested locally with Safari 👍 .

[ThomThomson]

Changes to inspector LGTM! Code only review.

[lukasolson]

This is a huge improvement! Spent some time playing around with it and this will be super helpful in narrowing down issues related to search. Just had one comment, more of a discussion rather than feedback.

[lukasolson]

This assumes we always want the request params being sent in the response - this will cause inflated responses most of the time even in cases where it's not used (e.g. the response from a GET request after the search has already been submitted). Can we make this so the behavior is opt-in, or at least remove these parameters from cases where the client should already have the request parameters?

[nreese]

How would this look? Would consumers of SearchSource pass in an option to turn-on request parameters?

[nreese]

I updated server side logic to avoid returning requestParams for async polling requests 3f1bc36

[nreese]

@elasticmachine merge upstream

[lukasolson]

LGTM!

[nreese]

@elasticmachine merge upstream

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 760fa74

Failed CI Steps

• FTR Configs #73

Test Failures

• [job] [logs] FTR Configs #73 / detection engine api security and spaces enabled - rule execution logic Machine learning type rules "before all" hook for "should create 1 alert from ML rule when record meets anomaly_threshold"

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
inspector	57	58	+1

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
data	2537	2542	+5

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
inspector	26.2KB	26.4KB	+203.0B

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
data	411.2KB	411.4KB	+198.0B
inspector	21.8KB	22.0KB	+176.0B
total			+374.0B

Unknown metric groups

API count

id	before	after	diff
data	3186	3193	+7

History

• 💛 Build #172606 was flaky e1dbd83
• 💔 Build #172590 failed 3f1bc36
• 💛 Build #171400 was flaky 788ee4d
• 💔 Build #171369 failed 0a9a113
• 💔 Build #171333 failed adc2e38

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