[Metrics UI] Replace date_histogram with date_range aggregation in threshold alert

[Zacqary]

Summary

Closes #100003

This switches Metric Threshold alerts from a date_histogram to a date_range in order to aggregate their data. This is in line with how Index Threshold alerts aggregate their data, and fixes an accuracy issue with gaps in document indexing.

It may also improve performance across all aggregation types.

Because this changes the way alerts evaluate, we should test this extensively to make sure it doesn't misfire existing alerts

Checklist

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

[elasticmachine]

Pinging @elastic/logs-metrics-ui (Team:logs-metrics-ui)

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 390bf91
• Storybooks Preview

Metrics [docs]

Unknown metric groups

References to deprecated APIs

id	before	after	diff
crossClusterReplication	8	6	-2
globalSearch	4	2	-2
indexManagement	12	7	-5
infra	5	3	-2
licensing	18	15	-3
monitoring	109	56	-53
total			-67

History

• 💔 Build #125734 failed a16b364

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

[estermv]

I've tested this and everything seems to work.

I created some alarms, with different aggregations (avg, rate, min, max), some with warning thresholds, and the alarms were triggered correctly.

Do you think there is something else that should be tested specifically? Otherwise, I think this can be approved.

[Zacqary]

@estermv That's probably good, I just get anxious about changes like these

We can merge if you wanna approve

[neptunian]

Is having the rate agg still use date_histogram a temporary fix or do we need to find a non derivative value at some point? Could the rate agg still possibly cause the inaccuracy issue until then?

[Zacqary]

I think the inaccuracy issue is exclusive to doc_count. Changing the aggregation for the rest was more of for the possible performance boost.

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create backports run node scripts/backport --pr 100004 or prevent reminders by adding the backport:skip label.

[jasonrhodes]

@Zacqary I assume we just missed this by accident, which is no big deal -- let me know if you have questions/concerns or if you ran into any problems with the backport, though.

[kibanamachine]

Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync.