[Profiling] Auto-abort requests

[dgieselaar]

Auto-abort requests when the user navigates away from the page or a new request is started.

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: f3bbf22

Metrics [docs]

Async chunks

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

id	before	after	diff
profiling	235.4KB	235.9KB	+455.0B

Page load bundle

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

id	before	after	diff
profiling	12.5KB	12.6KB	+145.0B

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

[rockdaboot]

I'll test tomorrow morning locally.
Are you sure that the Merge branch main commit isn't accidentally backported to 8.5 ?

[dgieselaar]

@rockdaboot yeah, that's no problem. The commit gets squashed and all that is left is the diff. That one gets backported. (Sorry other Tim R 🥲)

[timroes]

Nevertheless I find this a great enhancement. Let's not waste those resources for the query if the user already doesn't care about the response! Approve 🎉

[jbcrail]

Looks good and works as expected!

I tested these use cases:

• load tested using 10 parallel runs and then canceled after a few seconds
• switched back-and-forth between flamegraph and differential flamegraph multiple times for a large time range
• switched back-and-forth between TopN functions and differential TopN functions multiple times for a large time range

For all cases, the server requests were canceled and the "Request aborted" was logged. I did not see the server errors about aborted requests as I had seen previously.

It was difficult to test the TopN stacktraces since the requests completed so quickly.

[dgieselaar]

@timroes 😄 hope you're well!

[kibanamachine]

💚 All backports created successfully

Status	Branch	Result
✅	8.5

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation