[RAM] Bug ordering log KPI

[XavierM]

Summary

Fix: #142910

To resolve this problem, we are thinking about doing two thing:

• Make sure we get our latest run to build the KPI
• Move up the bucket size on the KPI query

We kind of worry about the memory when we changed the bucket to 10000. So we did some stats by using Buffer.byteLength(JSON.stringify(results));. The results below:
Bucket of 10000, we do have 5.9 Mb in memory of the node
Bucket of 5000, we do have 2.9Mb in memory of the node
Bucket of 1000, we do have 590 kb in memory of the node

Reviewer what do you think?

Checklist

• Unit or functional tests were updated or added to match the most common scenarios

[elasticmachine]

Pinging @elastic/response-ops (Team:ResponseOps)

[EricDavisX]

tested via the cloud build and this looks ok to me. i'm going to let the env sit for a while and check it again, when it's rule counts have gotten up to 10k+ runs

for now, screenshot from test cloud cluster:

[JiaweiWu]

LGTM! I'll test it a bit more next week but the code looks good

[lcawl]

UI text LGTM, thanks!

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 5dc44a8
• Cloud Deployment

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
triggersActionsUi	671.9KB	672.6KB	+770.0B

History

• 💚 Build #79488 succeeded 42b6133
• 💔 Build #78950 failed 8d49d18
• 💛 Build #78941 was flaky 8de7195

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

[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