What’s new in cost management

Based on customer feedback, the instructions for how to create an integration with Microsoft Azure were updated. The new version of the documentation reflects the latest changes to the Azure UI and aims to resolve customer pain points by being more clear and easy to follow.

There are two options when you create an integration: a basic path where you use unfiltered data, and an advanced path with filtered data. The instructions for both sections are updated.

To learn more about Azure and explore the new updates, go to Integrating Microsoft Azure data into cost management.

Unattributed Storage is a type of project that gets created when cost management is unable to correlate a portion of the cloud cost to an OpenShift namespace.

There are two scenarios where Unattributed Storage can happen:

To learn more about how to calculate Unattributed Storage in Azure, see Unattributed Storage project for Azure.

Costs associated with ingress and egress network traffic for individual nodes are now separated. A new project called network unattributed shows costs related to network traffic. You can use a cost model to distribute theses network costs in a similar way to platform and worker unallocated costs.

If you have an AWS savings plan for the EC2 instances running on OpenShift nodes, cost management uses the savings plan cost by default.

Customers noticed that cloud and OpenShift costs in cost management do not always match the data that is in the cloud provider’s console. Most of the time, this discrepancy is because there is a missing integration between the Hybrid Cloud Console and either the OpenShift cluster, or the cloud customer account. This missing integration creates discrepancies in billing and cluster data.

To help solve this discrepancy, we added two new views in the OpenShift details page of cost management:

You can now unify your tags by mapping ones that have similar or related meanings. This functionality offers greater flexibility and control over how you categorize and track your resources. Tag mapping reduces complexity, helps you have accurate reporting and analysis, and enhances consistency across your resources.

For example, imagine that you are tracking your environment spending across different platforms, each with its own naming conventions:

Platforms:

Variations in your key values:

With the tag mapping feature, you can seamlessly convert these key values under a single expected key, such as environment, to ensure that you are consistent in tracking your spending.

To learn about tag mapping, see Enabling and creating a tag mapping.

The Cost Management Metrics Operator is now supported on IBM Power® (ppc64le), IBM Z® (s390x), IBM® LinuxONE (s390x), and ARM (aarch64) architectures. Cost management for OpenShift on IBM Z® is not IFL aware.

We made several changes to the UI that affect how to update your cost management settings. Before, you updated your settings in the Red Hat Hybrid Cloud Console settings page. With this update, cost management has its own settings page.