-
Task
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
None
-
5
-
False
-
-
False
-
subs-swatch-thunder
-
-
-
Swatch Thunder Sprint 1, Swatch Thunder Sprint 2
At the moment, the tally summary producer logic is to emit messages with HOURLY granularity among other criteria as defined in here: https://github.com/RedHatInsights/rhsm-subscriptions/blob/4055a8a13c980572d56cdb7f1fb5c395bf6d205c/src/main/java/org/candlepin/subscriptions/tally/SnapshotSummaryProducer.java#L102
Open questions:
- should we keep the filter by any measurements? What about the service level filter? Hourly and Daily snapshots work the same or do we need to have a different filter for each?
Acceptance Criteria
- Emit snapshots with granularity DAILY
- Update the getCurrentlyMeasuredTotal to calculate the totalValue by DAILY or HOURLY, not always HOURLY (link)
Verify billing producer is filtering just to HOURLY summary
- blocks
-
SWATCH-3793 Implement logic to detect customer usage over usage
-
- Backlog
-
- is blocked by
-
SWATCH-3980 Create the initial component test structure for swatch-tally
-
- Release Pending
-