Is related to SWATCH-2691

Note: gauge/counter logic implementation is out of scope of this epic, because it only becomes relevant during deduplication

• Receive and verify a sample Event message from the ansible team after they've completed the linked blockers about field names
• Validate/go through the AAP Swatch Test Plan]
  • Event ingestion
    • Adjustments
      • dedup is an entirely different epic, but adjustments also provide dedup behavior.  where is the line for how much adjustment logic should be applied for events with the AAP product tag
  • Hourly tally
  • Behavior when that instance already has been seen by nightly tally
  • Behavior if nightly tally encounters an instance after it's been hourly tallied
  • billable usage
    • is contract use supported?
    • aws dimension names align and producers are successful in posting usage to cloud providers

https://docs.google.com/document/d/1Uod__RKPA-ZkHNQHVdLJVz9nd_UbZkqAM3jlrQBX2to/edit

Done:

• iqe code landed in main branch of iqe-rhsm-subscriptions-plugin to validate the behaviors outlined above (collaboration encouraged)
  • if backend work is incomplete, disable the failing tests until the prerequisite work is completed.