-
Task
-
Resolution: Done
-
Normal
-
None
-
None
-
None
-
3
-
False
-
-
False
-
subs-swatch-lightning
-
-
-
Swatch Lightning Sprint 4
In SWATCH-3792, we created the swatch-utilization skeleton with some basic functionality only.
After SWATCH-3789, we can now properly configure the utilization summary consumer to consule objects of UtilizationSummary.
Acceptance Criteria
- Use the UtilizationSummary model created in
SWATCH-3789 - Validate the payload to ensure we're sending all the required fields (orgID, productId, metricId, for non payg products. For payg products, also the billing_account_id). Log a warning when we receive a message with a wrong productId or metricId.
- Configure/Add the utilization summary consumer to listen these messages.
- All "TODO: ...
SWATCH-4005" comments that were committed (SWATCH-4001) are handled and removed.
- blocks
-
SWATCH-3793 Implement logic to detect customer usage over usage
-
- Review
-
- is blocked by
-
SWATCH-3789 Add tally snapshot consumer in swatch-contracts to set the capacity
-
- Closed
-