microsoft / microsoft/finops-toolkit

[AOE] Every workbook using a costs lookback period should consider the 3-days costs ingestion offset

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

Nobody has claimed this yet.

Good first issue 🏆 Tool: Optimization Engine Type: Feature 💎
Dominant language
PowerShell
Stars
603
Forks
248
Avg merge
7d 11h
Merged PRs (30d)
11

Description

⚠️ Problem

Some AOE Workbooks, such as the Benefits Simulation, Reservations Potential, Reservations Usage and others, have a costs lookback period that is set as 30 days by default. However, as the engine has a default 3-days offset for ingesting costs, the workbooks always base their results in a shorter lookback period (e.g., 27 days for a selected period of 30 days). NOTE: the ingestion offset is set as an Azure Automation variable that cannot be read from the workbooks.

🛠️ Solution

The aforementioned workbooks should add a disclaimer or even a costs offset parameter that would add the offset time range to the lookback period, so that users get more accurate results.

🙋‍♀️ 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 by reviewing the Benefits Simulation, Reservations Potential, and Reservations Usage workbooks and how their 30-day costs lookback is configured. Confirm how the 3-day ingestion offset affects each workbook, then clarify whether the accepted outcome is a disclaimer or an offset parameter; done means the affected workbooks consistently account for the offset.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
analytics, cloud
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.