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

Create new Billable Usage aggregate table

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Obsolete
    • Icon: Undefined Undefined
    • None
    • None
    • swatch-billable-usage
    • None

      Create a new billable usage aggregate table with columns in swatch-billable-usage.

      billable_usage_aggregate table

       

      Column Value Nullable
      aggregate_uuid BillableUsageAggregate.aggregateId N
      aggregated_usage_timestamp BillableUsageAggregate.windowTimestamp N
      markteplace_timestamp timestamp from marketplace api response Y
      marketplace_dimension dimension from marketplace api response Y
      value BillableUsageAggregate.totalValue N
      Status BillableUsageAggregate.status N
      customer_reference_id aws UsageRecordResult.CustomerIdentifier Y
      usage_record_id MeteringRecordId(aws) or UsageEventId(azure) Y
      retry_after Set by BillableUsageStatus consumer Y
      error_code BillableUsageAggregate.status Y
      sent_to_billing_provider_timestamp previously BillableUsageAggregate.billedOn Y
      org_id BillableUsageAggregateKey.orgId N
      billing_provider BillableUsageAggregateKey.billingProvider N
      billing_provider_account_id BillableUsageAggregateKey.billingAccountId N

       

      Done:
      **

      • Table created
      • No functional changes

       

       

       

      Notes:

      • Aggregate_uuid
      • aggregated_usage_timestamp)
        • The hour we are choosing for that aggregate….what timestamp we’re associating that usage to on the marketplace system (ideally the hourly snapshot) (window_timestamp)
      • customer/product/dimension/value per hour
      • effectiveStartTime (Azure time that the usage was for)
      • Dimension (marketplace_dimension)
      • Value
      • Status (Customerreference_status?)
        • attribute of the aggregate
      • Customerreference_id
      • Identifier for that customer for that billing provider
      • Usage_record_id
        • MeteringRecordId or usageEventId
      • Retry_after (moved)
      • Error_code (moved)
      • aggerate_sent_to_billing_provider_timestamp (moved)
      • Related to the communication of the message to the marketplace - before sending, acknowledge, something like that
      • messageTime (Azure accepted)
      •  
      • Org_id (duplicate)
      • Billing_provider
      • billing_provider_account_id

       

              Unassigned Unassigned
              karshah@redhat.com Kartik Shah
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: