Is your proposal related to a problem?

My feature request is related to the following bug ticket: #7070

After further investigation I came to the conclusion that the setting max_source_resolution in the http request is the solution.
The ruler, as it stands now, only calculates data using auto downsampling. This is an issue, as the querier then only uses raw data for calculating rules. As I want to calculate metrics aggregated across a long time period this becomes a problem, since my raw data only exists for 7 days.
For example with the following query: increase(kong_http_requests_total[14d])
The ruler will only be able to calculate the last 7 days instead.

Describe the solution you'd like

The solution I found was setting max_source_resolution=5m. This will force the querier to use the downsampled data which allows the ruler to get all data it needs for the aggregation.

I tested this by setting MaxSourceResolution manually in the code of the ruler and creating my own image:

	v, warns, err := promClient.PromqlQueryInstant(ctx, endpoints[i], qs, t, promclient.QueryOptions{
		Deduplicate:             true,
		PartialResponseStrategy: partialResponseStrategy,
		Method:                  httpMethod,
		DoNotAddThanosParams:    doNotAddThanosParams,
		MaxSourceResolution:     "5m", // this would need to be retrieved by a flag

The flag could be something like: --query.max-source-resolution

After this is implemented, I am expecting to see my requests calculated like this:

Ignore the gaps please. As you can see, the metric is calculated correctly again, before the switch we made.

For more context, please read the bug ticket.