title: Prometheus range query rounding off time when used with resolution step
body: <p>I have a prometheus metric called http_requests_total which is scraped every 30s. I have created a recording rule to aggregate it at an hourly interval for my UI dashboard. Let's call this new metric increase_http_requests_total_60m.</p>
  <p>I want to use this aggregated metric to further aggregate and create increase_http_requests_total_1d. My idea to do this is to do - sum_over_time(increase_http_requests_total_60m[1d:60m]).</p>
  <p>However, I realized that the value is coming to be different as compared to increase(http_requests_total[1d]). Upon diving deeper, I realized that increase_http_requests_total_60m[1d:60m] gives me data points which are exactly on the hour i.e. 6pm, 7pm, 8pm, etc. How can I make it so that the data points are actually - now, now - 1hr, now - 2hr, etc.?</p>
  <p>Open to other ideas as well to achieve my end goal.</p>