Uploaded image for project: 'Subscription Watch'
  1. Subscription Watch
  2. SWATCH-2183

Design Billable Usage Aggregation Process

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • BIZ-629 - ELS add on for concurrent (non-pay-as-you-go) RHEL offerings

      In order to handle both AWS and Azure limitations on only having one usage event per hour, we need to design a way to aggregate billable_usages for a given hour. 

      Questions to address:

      • Where should the aggregation occur?
        • tally-worker?
      • What timestamps are being sent to the marketplaces?
      • Can we use in-memory aggregation without extra topics

       

      AC: 

      A PoC has been completed for using kstreams here:
      https://github.com/RedHatInsights/rhsm-subscriptions/pull/3012 

              kflahert@redhat.com Kevin Flaherty
              kflahert@redhat.com Kevin Flaherty
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: