-
Task
-
Resolution: Unresolved
-
Minor
-
None
-
None
-
False
-
-
False
-
subs-swatch-lightning
-
-
At the moment, we're sending messages to the kafka topic "platform.rhsm-subscriptions.billable-usage-hourly-aggregate" like:
{
"windowTimestamp": "2023-12-21T01:10:28Z",
"aggregateId": "e81bc918-6434-4a58-9192-8a8dd73ec8fb",
"aggregateKey": {
"orgId": "org123",
"billingProvider": "azure",
"metricId": "Cores",
"productId": "rosa"
}
}
These messages are consumed by the swatch-producer-aws and swatch-producer-azure services instead of only the swatch-producer-azure service (because the "billingProvider" is "azure"). This situation is generating a lot of noise in traces and unnecessary network traffic.
We need to find a better and more efficient solution. Probably, the easiest and more scalable solution is to use dedicated topics for aws and azure.
- depends on
-
SWATCH-3233 Refactor hourly aggregation of billable usages
-
- Backlog
-
- incorporates
-
SWATCH-3245 Set the group-id when producing/consuming the remittance aggregations
-
- Closed
-