You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This data is imperative for any kind of reporting/automation around different commitment types such as Reserved Instances or Savings Plans.
Which area does this issue relate to?
A: Missing FinOps feature, use case, or scenario
Detailed Description
In the current FOCUS data, some of the vital information around commitment types is not available such as commitment_quantity, commitment_start_time, and commitment_end_time.
This is of crucial importance as it can help the FinOps analysts in planning their upcoming commitments if they are aware of a commitment expiring in the recent future.
What use cases, FinOps or others, can't be performed with the existing specification unless this issue is addressed?
The most common use case that's getting affected due to this limitation is not having the visibility into commitments that are due for expiration in the near future. This limits the FinOps team from performing any kind of an automation around their commitment plans.
Which FinOps personas does this issue relate to?
Practitioner, Engineering
Which provider groups or specific providers does this issue relate to?
All CSPs
On a scale of 1 - 4, how critical is this for your organization?
2: Important for adoption in the next 3-6 months
Objective
No response
Data Examples
No response
Issues, PRs, or Other References
No response
The text was updated successfully, but these errors were encountered:
Summary
This data is imperative for any kind of reporting/automation around different commitment types such as Reserved Instances or Savings Plans.
Which area does this issue relate to?
A: Missing FinOps feature, use case, or scenario
Detailed Description
In the current FOCUS data, some of the vital information around commitment types is not available such as commitment_quantity, commitment_start_time, and commitment_end_time.
This is of crucial importance as it can help the FinOps analysts in planning their upcoming commitments if they are aware of a commitment expiring in the recent future.
What use cases, FinOps or others, can't be performed with the existing specification unless this issue is addressed?
The most common use case that's getting affected due to this limitation is not having the visibility into commitments that are due for expiration in the near future. This limits the FinOps team from performing any kind of an automation around their commitment plans.
Which FinOps personas does this issue relate to?
Practitioner, Engineering
Which provider groups or specific providers does this issue relate to?
All CSPs
On a scale of 1 - 4, how critical is this for your organization?
2: Important for adoption in the next 3-6 months
Objective
No response
Data Examples
No response
Issues, PRs, or Other References
No response
The text was updated successfully, but these errors were encountered: