- 
    Bug 
- 
    Resolution: Done
- 
    Major 
- 
    None
- 
    None
- 
        5
- 
        False
- 
        
- 
        False
- 
        subs-swatch-lightning
- 
        
- 
        
- 
        Swatch Lightning Sprint 1, Swatch Lightning Sprint 2, Swatch Lightning Sprint 3
This card is outcome of investigation from SWATCH-3867
SWATCH currently has logic to handle cases with incorrect dimensions, but it requires a product tag match. Since these dimensions are non-configured in SWATCH and doesn't have a product tag, we are unable to filter them with the existing logic. Example when we get a sku with a non configured product tag and then dimension is MCT4545
I was able to replicate the issue by calling API as below:
curl -X POST http://localhost:8011/api/swatch-contracts/internal/contracts \ -H "Content-Type: application/json" \ -d '{ "partner_entitlement": { "rhAccountId": "org123", "sourcePartner": "aws_marketplace", "entitlementDates": { "startDate": "2023-05-24T18:46:05Z", "endDate": "2026-09-24T12:46:10.229Z" }, "rhEntitlements": [ { "subscriptionNumber": "14968327", "sku": "BASILISK" } ], "purchase": { "vendorProductCode": "cmjyuylkjymet72qluirawh6v", "contracts": [ { "dimensions": [ { "name": "MCT4545", "value": "600" } ] } ] }, "partnerIdentities": { "awsCustomerId": "W4TpJBpJKhD", "sellerAccountId": "403771435366", "customerAwsAccountId": "771835612317" } }, "subscription_id": "sub14968327" }'

AC:
- We should filter invalid dimensions when there is no matching product tag
- Log filtered data with info level
- Component test in swatch contract around this functionality
- blocks
- 
                    SWATCH-4015 Data Cleanup for Invalid metric_id in contract_metric Table -         
- Backlog
 
-         
- is related to
- 
                    SWATCH-3867 Subscription_measurements missing data from contract_metrics -         
- Release Pending
 
-         
| 1. | Component Tests |  | Release Pending |  | Kartik Shah | 
