microsoft / microsoft/finops-toolkit

Add the foundations for an extensible cost optimization recommendations pipeline framework

Open
#1,224 0 comments 0 reactions 1 assignee View on GitHub

@helderpinto is already working on this.

Since Dec 20, 2024.

Status: 🔄️ In progress Tool: FinOps hubs Tool: Optimization Engine Type: Feature 💎
Dominant language
PowerShell
Stars
603
Forks
248
Avg merge
7d 11h
Merged PRs (30d)
11

Description

📝 Scenario

As a FinOps Practitioner using FinOps Hubs, I need to have a centralized list of cloud provider-generated and custom cost optimization recommendations with an historical perspective in order to be able to prioritize rate and usage optimization tasks based on potential savings and historical relevance.

💎 Solution

The Workload optimization and Rate optimization reports will include pages dedicated to cost optimization recommendations, not only coming from Azure Advisor, but also from custom recommendations based on Azure Resource Graph KQL queries (similar to the ones available in the Cost Optimization Workbook). Those pages will provide not only the latest available recommendations but also an historical perspective of how long those recommendations have been made.

📋 Tasks

Required tasks
Stretch goals
  • Hubs deployment automation to assign the required permissions to the Azure Data Factory identity.
  • Enrich recommendations information presented in the reports by correlating with costs data.
  • Document how to extend Hubs by bringing in externally generated recommendations

ℹ️ Additional context

The solution must allow for easily adding new custom recommendations in future releases.

🙋‍♀️ 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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.