Details
-
Bug Part
-
Resolution: Done
-
L3 - Default
-
None
-
Not defined
Description
Context:
Currently running instances can be missing in the result of the groupByDuration report if these make up the global maximum among all durations.
This is due to how the filter that should prevent too many buckets is created in `createLimitedGroupByScriptedDurationAggregation` by first determining global min/max values that are used to define the filter window to perform the duration aggregation on. However due to the new max duration value of any running instance when the actual report evaluation is performed that filter will miss the particular instances that exceeded the former max already.
AT:
- running instance(s) that make up the global maximum should be in the groupByDuration result given they fit in the last bucket at the time of evaluation