Summary:

• Determine how we might implement a scope or range of data request to avoid long operations.

Goal:

• Currently, CloudKitty Processor does a whole calculation when it first starts that entails searching for metrics each "period" between the 1st of the Month and "now". This operation can take more than 40 minutes especially in the last days of the month.
• This is very bad for testing, as makes testing of the Processor almost impossible. However, that "1st of the Month" date can be superseded patching the Scope and supersede the "last_processed_timestamp" to something that suits us, like 2 hours ago.
• Then, the Processor will only process between that "last_processed_timestamp" to now, which will be very useful for CI testing.
• It is useful for CI, but it can also be useful to provide workarounds over certain edge cases.

TimeBox:

• TBD

Deliverables/Outcomes:

• There will be instructions on how to create a Scope with an arbitrary "last_processed_timestamp" for CI usage
• Creation of Feature that covers the overview for what would need to be refined and scoped for delivery of the functionality in question.