The current implementation of Loki in CloudKitty does just one query per time the user wants to get the generated report. As CloudKitty always works in month-based chunks, this means that the max_query_length must be 745h or bigger, so we can search results in the worst possible case, which is the user generating a report of a whole 31-day month.

The Red Hat Loki Operator does not support changing this parameter, so we are stuck with the default maximum, which is 7 days.

The proposed solution is to shard queries launching more queries with shorter periods. For example, Grafana uses by default a query per day. We must modify CloudKitty Loki integration to do sharding if we want it to be working with Red Hat Loki's provisioned operator.