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

Engage with the performance team to measure our capacity for end to end integration between the tally service to the notification service.

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • None
    • None

      The projected message volume for processing, based on data up to 2025-05-24, is significant:

      • Daily Snapshots: Approximately 75,000 messages per day.
      • Hourly Snapshots: Approximately 18,000 messages per hour.

      Therefore, we need to ensure our current solution supports this amount of data to be handled.

      The idea is to generate N events that implies a customer over usage, then trigger the tally for these events and watch how long takes to the notification message to be sent for these N events/customers.

       

      If it hasn't been done already, the perf namespace is going to need to be updated to deploy the swatch-utilization service: https://gitlab.cee.redhat.com/service/app-interface/-/blob/master/data/services/insights/rhsm/cicd/deploy-perf-clowder.yml?ref_type=heads 

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

                Created:
                Updated: