microsoft / microsoft/finops-toolkit

FOCUS Export inconsistant vcore information

Open
#1,209 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Resolution: External Resolution: Support request Tool: Cost Management Tool: FOCUS
Dominant language
PowerShell
Stars
603
Forks
248
Avg merge
7d 11h
Merged PRs (30d)
11

Description

🐛 Problem

In the Focus Export, where chargeDescription = "sql database singledb/elastic pool hyperscale - compute gen5" the line item does not provide any indication of the number of vcores attributed to the resource.

in contrast where chargeDescription = "sql database single/elastic pool business critical - compute gen5" then column x_skudetails has a key value pair of "vcores":16.

it appears that the availability of this information is inconsistant based on the SQL tier provisioned in Azure.

👣 Repro steps

TODO: Add repro steps below:

  1. Go to Cost Management and Billing
  2. Export FOCUS 1.0

🤔 Expected

column x_skudetails has a key value pair representing the number of vcores. example: "vcores":16.

🙋‍♀️ Ask for the community

We could use your help:

  1. Please vote this issue up (👍) to prioritize it.
  2. Leave comments to help us solidify the vision.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the FOCUS 1.0 export from Cost Management and Billing, comparing the two SQL chargeDescription examples in the issue. Trace how x_skudetails is populated for the hyperscale and business critical tiers; done means the hyperscale line item also includes a vcores key-value pair when that information is available.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, powershell
Domain
cloud, data
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.