The pricing-gap DLQ

WHAT HAPPENS WHEN A PRICE IS MISSING:

  Cost rule evaluates the resource
    → no usable price for its type
    → no recommendation is shown (no guess, no $0 card)
    → the gap is logged on ZopDev's side
    → next pricing sync adds the rate
    → the next evaluation shows the recommendation

NOT AFFECTED BY A PRICING GAP:
  Orphan findings      an unattached disk is worth cleaning up
                       whether or not it can be priced
  Posture findings     compliance, security, reliability,
                       governance and performance keep their
                       rule-declared severity; no dollar figure
                       is involved

CASE A: the resource never had a recommendation
  Recommendations list: nothing for that resource yet
  Resource still appears in inventory and cost views
  Once the rate lands: the recommendation shows up
  on the next evaluation, with its savings figure

CASE B: a recommendation was open, then its price went missing
  The finding is closed with the reason "No price data"
  Its history explains: the saving could not be verified,
  so it was closed rather than shown as an unverified number
  Once the rate is back: the finding can be raised again

CAUSE 1: NEW SKU
  Cloud provider releases a new instance type or storage class
  Example: a new instance family launches mid-month
  Pricing sync runs weekly; it hasn't fetched the rate yet
  TYPICAL DURATION: up to about a week; clears on its own

CAUSE 2: NEW REGION
  You start running resources in a region you did not use before
  The next pricing sync picks up its rates
  TYPICAL DURATION: up to about a week; clears on its own

CAUSE 3: RARE COMBINATION
  Unusual region + SKU + OS combination not in the public price list
  Example: a storage redundancy option in a less-common region
  The gap is structural; it won't clear on its own
  TYPICAL DURATION: until ZopDev engineering adds coverage

THE INTERNAL LIST TRACKS:
  Rule that wanted a price
  Resource type, provider and category
  When the gap was first and last seen
  How many times it has occurred

RAISE A REQUEST WHEN:
  A resource type you run in volume never shows a savings
  figure, while similar types do
  The gap has lasted longer than two weekly pricing syncs
  Findings closed with "No price data" keep recurring

INCLUDE:
  Provider, resource type or instance size, region
  How many resources you run of that type
  When you first noticed (a date)
  Any finding closed with "No price data", if you have one

DON'T RAISE A REQUEST WHEN:
  The type launched in the last week (cause 1)
  You only just started using the region (cause 2)
  The resource has only orphan or posture findings

MONTHLY REVIEW (Q2 2026):

T+0      Open Recommendations; filter to Rightsizing
         Compute rightsizing findings look normal for
         most instance families

T+2 min  Notice: 40 VMs of a newly launched instance family
         show no rightsizing or idle findings at all
         Several sit near 3% CPU in the Metrics drawer
         Family launched 5 days ago
         Decision: likely cause 1 (new SKU); wait one week

T+4 min  Notice: 120 storage accounts using one redundancy
         option in a less-common region
         No savings figure has ever appeared for them
         Same option in other regions shows findings
         Decision: likely cause 3 (rare combination)

T+6 min  Check history on one storage account
         An older finding closed with "No price data"
         Confirms the gap is pricing, not the estate

T+8 min  Raise a support request:
         Provider: Azure
         Type: storage account, that redundancy option
         Region: the less-common one
         Count: 120 resources
         First noticed: this review
         Evidence: one finding closed with "No price data"

T+1 week Re-check:
         New instance family: rightsizing findings now present
         (weekly sync added the rate)
         Storage accounts: still no figure; support confirms
         engineering is adding coverage

T+1 month Re-check at next review:
         Storage accounts: findings now present

□ STEP 1: Open Recommendations; filter to one cost category
  (rightsizing or idle)
  Category: __________

□ STEP 2: List resource types you run in volume
  Type 1: __________   Count: _____   Findings? □ Yes □ No
  Type 2: __________   Count: _____   Findings? □ Yes □ No
  Type 3: __________   Count: _____   Findings? □ Yes □ No

□ STEP 3: For each type with no findings
  Launched or adopted in the last week? □ Yes □ No
  New region for you? □ Yes □ No
  Metrics suggest waste anyway? □ Yes □ No

□ STEP 4: Look for "No price data" closures
  Finding history checked for: __________
  Found any? □ Yes □ No

□ STEP 5: Decide
  Wait (cause 1 or 2): _____ types
  Raise a support request (likely cause 3): _____ types
  Details ready: provider, type, region, count, date □