Uploaded image for project: 'Cost Management'
  1. Cost Management
  2. COST-5575

Emit events to swatch using "metric_id" instead of "uom"

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Normal Normal
    • 2024-Oct-11, 2024Q4
    • None
    • None
    • None
    • 5
    • False
    • None
    • False

      We're receiving events from cost-management like:

      {
  "event_source": "cost-management",
  "event_type": "snapshot",
  "account_number": "123",
  "org_id": "456",
  "service_type": "RHEL System",
  "instance_id": "i-iiiii",
  "timestamp": "2024-10-05T06:00:00Z",
  "expiration": "2024-10-05T07:00:00Z",
  "measurements": [
    {
      "value": "4",
      "uom": "vCPUs"
    }
  ],
  "cloud_provider": "AWS",
  "hardware_type": "Cloud",
  "product_ids": [
    "69",
    "204"
  ],
  "sla": "Premium",
  "usage": "Production",
  "billing_provider": "aws",
  "conversion": "false",
  "role": "Red Hat Enterprise Linux Server",
  "billing_account_id": "xxxx"
}

      Swatch deprecated the measurements.uom property in favour of measurements.metric_id (for more context, see SWATCH-1394).

      Acceptance Criteria

      • Emit events using "metric_id" instead of "uom"

              mskarbek Michael Skarbek
              jcarvaja@redhat.com Jose Carvajal Hilario
              Eva Šebestová Eva Šebestová
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: