Skip to main content
Aria Knowledge Central

Monetized Usage Record Sync

Aria Allegro monetizes usage records, aggregates them to control volume, and then syncs them with Core Aria using a batch-size setting to call the bulk_record_usage_m API. The following describes the component architecture for this sync process.

murs-01.png

Scheduler

The Scheduler uses the Billing Aggregate configuration to determine how often to synchronize monetized usage records. It calls the Core Service to manage aggregated usage.

Allegro Operations Service

The Scheduler invokes the Allegro Operations Service to perform the following.

  1. Refers to the Aggregate Monetized Usage configuration to determine whether aggregation is required. If so, it uses the configuration to identify the attributes to aggregate.
  2. Finds all monetized usage records not yet synchronized.
  3. Aggregates usage records using the configuration.
  4. Creates aggregated usage records.
  5. Updates monetized usage in batches with the aggregate ID to link aggregated usage to monetized usage. Batch size is a system configuration parameter that controls the batch size used with the bulk_record_usage_m API.
  6. Publishes each batch ID to the Kafka topic for the Aria Allegro Sync Service to consume.

Aria Allegro Sync Service

The Aria Allegro Sync Service consumes aggregate usage IDs from the Kafka topic and performs the following.

  1. Reads the batch ID from the Kafka topic and fetches all aggregated records for the batch.
  2. Makes a synchronous Core Aria bulk_record_usage_m API call.
  3. Updates the success or error status for each aggregated usage record in the batch based on the Core Aria API response.
  4. Makes records with errors available for later reprocessing.
  5. Repeats this process in parallel for all batches created.

Allegro UI lets you review and reprocess aggregated monetized usage records that failed to synchronize.

TOP
  • Was this article helpful?