Partner | Control Over Support Ticket Routing in Customer Tenants

We have released a new feature in customer tenant setup that allows partners to hide the “Submit a Ticket” link within a channel tenant. If "Off," partners will still be able to open tickets using this option when in the partner tenant. This toggle can be found in Setup -> Admin -> Settings.

Kubernetes Cost History Report for FlexOrgs – Public Beta

We are excited to announce the public beta release of our Kubernetes Cost History Report that is visible at the sub-organization level in FlexOrgs. This report is supported for Kubernetes running on AWS and Azure with the VMware Aria Cost collector agent installed on them. You can access these reports by going to Reports -> Containers -> Kubernetes Cost History. Key Benefits & Use Cases:

1. Chargeback: FinOps teams can view “cost per X” and report to business leaders at the required granularity. With a single click, costs can be allocated based on container requests or based on actual resource usage, so complete and accurate chargeback of shared costs can be implemented.

2. Showback: FlexOrgs users in sub-organizational units can now access container cost data. With this visibility, engineering teams can see the cost of the individual containers and workloads that they own. Used in conjunction with our Kubernetes rightsizing recommendations, engineers can easily optimize container requests to drive down costs.

3. Extensibility: The Kubernetes Cost History Report is backed by FlexReports and can be accessed via the FlexReports API. This enables businesses to extend K8 cost data to integrate with other business systems, processes, and workflows.

Update to Anomaly Detection – Save & Subscribe

One of our most requested features for Anomaly Detection reports, Save & Subscribe, is now available across AWS, Azure, and GCP.  With this update, users can receive cost anomaly reports by email at their desired frequency so they can keep a pulse on potential wasted spending.

To save and subscribe to a report, first go to Governance -> Anomaly Detection. Select a cloud and filter by the following parameters: timeframe for evaluation, account name, service, region, and cost impact. Then click Actions -> Save As and create a name for the report.

To subscribe to the saved report, go to Reports -> Saved Reports in the left-side navigation pane. Find the report you just created and click on the report name. Click "Subscribe," "New Subscription," and enter your desired specifications for report delivery.

This update unlocks new parameters for anomaly reporting, including:

• Service-specific cost anomaly alerts

• Region-specific cost anomaly alerts

• Marketplace-specific cost anomaly alerts

• Custom evaluation timeframe up to 90 days

Additionally, the policy engine can still be used to create alerts when the cost impact of an anomaly reaches a specified dollar amount or a specified percentage increase or decrease.

Updates to IAM Policy For Amazon AppStream

In a future release, we will be adding support for Amazon AppStream Images and AppStream Applications. To prepare for this change, customers need to update their IAM policy to contain the following permissions:

• appstream:Describe*

• appstream:ListTagsForResource

OR

• appstream:ListTagsForResource

• appstream:DescribeApplications

• appstream:DescribeImages

Update to CloudService GraphQL Metadata API for Direct and Indirect Service Retrieve

The CloudService API provides a comprehensive list of cloud services utilized on our platform, categorized by cloud type (AWS, Azure, GCP). Previously, there was no built-in capability to differentiate between the two types of cloud services: direct and indirect. As a result, the API response would return the entire list of cloud services specific to a particular cloud type, requiring manual filtering on their end.
To address this limitation, we are introducing a new filter. By incorporating filter parameters into the API requests, we can now retrieve either direct or indirect services or the complete list directly from the API. This eliminates the need for manual filtering after receiving the response. Learn more in the product documentation.

Direct Cost

Indirect Cost