v2 Metric Series Resolution Discrepancy

[pjn]

Hi

I am seeing unexpected results when querying time series metrics at differing resolutions. There is clearly something I don't understand, but I can't put my finger on it.....

I am querying time series with a 10m resolution and expecting that the same query at 1h resolution would be an aggregation of the 10m values.

The API call uses the following parameters:-

metricSelector=builtin:apps.web.activeSessions:filter(eq("dt.entity.application","APPLICATION-XXXXXXXXXXXXXXXX")):splitBy()
from=2022-11-22 00:00
to=2022-11-23 00:00
resolution=10m

and returns the following results:-

22/11/2022 00:10 69
22/11/2022 00:20 61
22/11/2022 00:30 48
22/11/2022 00:40 53
22/11/2022 00:50 42
22/11/2022 01:00 38
22/11/2022 01:10 33
22/11/2022 01:20 39
22/11/2022 01:30 28
22/11/2022 01:40 23
22/11/2022 01:50 13
22/11/2022 02:00 16
22/11/2022 02:10 19
22/11/2022 02:20 29
22/11/2022 02:30 21
22/11/2022 02:40 29
22/11/2022 02:50 22

and the same query with 1h resolution says:-

22/11/2022 01:00 266
22/11/2022 02:00 125
22/11/2022 03:00 117

I can't reconcile the 1h figures with the 10m ones. They are not a sum or average; I'm confused.

Can anyone help shed light on this?

Thanks
Paul

[DanielS]

I've been following this, but I guess that open a support ticket for this would be the best option, just in case this lead to a possible bug. Thanks