Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

💡 Feature Request - Price estimate for implementing WARA recommendations #565

Open
reiantonio opened this issue Dec 11, 2024 · 1 comment
Labels
Enhancement 🆕 New feature or request

Comments

@reiantonio
Copy link

Describe the solution you'd like

My customer recently requested that we include a column detailing the cost of implementing a specific WARA recommendation. This addition would assist them in understanding the financial implications and facilitate internal planning before making any commitments.

Describe alternatives you've considered

Utilizing the Azure Pricing Calculator may not offer the detailed granularity that the customer requires.

Additional context

N/A

@microsoft-github-policy-service microsoft-github-policy-service bot added the Enhancement 🆕 New feature or request label Dec 11, 2024
@FallenHoot
Copy link
Contributor

I appreciate the effort to explore more accurate cost estimations for cloud workloads. However, I have some concerns regarding the reliability of querying the Azure Price REST API for ongoing cost predictions.

While the Azure Pricing Calculator pulls data from this API, it requires authentication to the customer’s account to reflect accurate pricing based on their specific discounts. Without this, the estimates are limited to PAYGO prices, which may not align with the customer's actual costs. As a result, relying on the API alone might not provide enough data for consistent, reliable ongoing cost estimations. Not to mention depending on the workload, we could be talking about several hundred datapoints that could be known or unknown. Resulting in the query's to handle a lot of exceptions and assumptions.

Additionally, while CICD methods such as TheCloudTheory/ACE for BICEP and InfraCost for Terraform give a good high-level estimate of price differences before deployment, they still have limitations. These tools offer rough cost predictions, but they do not provide precise, 1:1 price estimates. Could be a nice middle ground to use those tools.

In my experience, the critical factor when estimating costs is aligning workload requirements with reliability goals.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement 🆕 New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants