The issue is observed on the dashboard.
Metric queries with a time range greater than 24 hours result in data loss.
For e.g. queryA-1day.json contains more data (over 24 hours) than queryA-2day with the same query over the last 48 hours because the latter is clearly missing data points.
DX SAAS : 25.10.1/25.11.1
We cannot assume larger time range should always return more data points.
This is only true if the query always uses same frequency, which is not the case.
Checking the 2 sample query of 1-day and 2-day:
"frequency": 300
vs.
"frequency": 900
Meaning each data point in 2-day query represents 900s (15m) of data, like combined 3 data points of 300s(5m) in 1-day query.
This is why the 2-day query actually returns less data points.
The 2-day query will return less data points than 1-day/24-hour due to different frequency
So
7-day query the default frequency is 3600, which is one hour;.So for 7-d, you can get max 7*24=168 data points
for 24-h, the frequency is 5m, so you can get max 24*12=288
for 48-h, the frequency is 15m, so you get 48*4=192
For query frequency, by default, it's auto for source Metrics. You can edit the Panel to change it.
Note: Be careful setting fixed frequency as clamps can be hit when querying a big time window with small frequency.
For the doc, search for "Frequency" here: