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

Spike: Investigate if we can submit multiple usages to AWS Marketplace

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • swatch-producer-aws
    • False
    • Hide

      None

      Show
      None
    • False
    • subs-swatch-lightning

      At the moment, when usages are aggregated by hourly and org ID in the billable usage service, the aggregated usage is sent to either swatch-producer-aws or swatch-producer-azure depending on the billing provider. In this task, we'll focus only in swatch-producer-aws.

      In swatch-producer-aws, the aggregated usage is then submitted to AWS using the Batch Meter API: https://docs.aws.amazon.com/marketplace/latest/APIReference/API_marketplace-metering_BatchMeterUsage.html.

      This API seems to be designed to send multiple usages for different customers. However, we are only submitting one usage which is causing that we hit the marketplace rate limit quite often: SWATCH-3449

      This task is about to analyse solutions in swatch-producer-aws to group different usages of customers and send it at once using the same API.

      Note that at the moment, we're sending around 1200 messages per hour, so the idea is to keep the number lower than 500 to avoid hitting the rate limit error.

              Unassigned Unassigned
              jcarvaja@redhat.com Jose Carvajal Hilario
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: