Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.
Chapter 4. April 2024
4.1. Cluster info
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:
- The Cluster information view shows details about your cluster such as the cluster ID, the Cost Management Metrics Operator version and if there is an update available, and links to your integrations.
- The Data details view shows your data processing states. These states inform you if data is already processed, is currently processing, or has errors. If you have a linked cloud integration for a cluster, it also displays the processing states for supported clouds.
4.2. Tag mapping
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:
- GCP
- OpenShift
- AWS
Variations in your key values:
-
env -
environment -
Environment
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.
