The section discusses different ways of managing perspective groups.
To delete an empty group, use Clean Empty Groups.
You can delete a perspective group only if it is not an individual dynamic group. When you delete a group, VMware Tanzu CloudHealth notifies you of any subscriptions or cost reallocation rules that are tied to that group.
The classification rule that gathered the assets in the deleted group is no longer evaluated.
You can merge multiple individual groups that have the same intended collection of assets. For example, if you have a perspective called Owner that gathers assets into groups named after individual asset owners in your organization, the classification rule gathers assets based on the unique values of the owner tag. To merge two groups, select both groups and click the link icon. In this example, due to inconsistent tagging practices, assets belonging to Vikram are tagged as owner
= Vikram
sometimes and as owner
= vikram
at other times. The classification rule creates two groups -Vikram and vikram - to gather these assets. You can merge these two groups so that assets that meet the condition of either rule are gathered in the same group. In this way, changes, additions and deletions to assets within this group will accurately reflect assets tagged with either owner = Vikram
or owner = vikram
. To unmerge groups, click the unlink icon next to the merged group. Unmerging groups removes all previously linked groups from the merged group.
Note: Groups cannot be unmerged if the resulting subgroups would have identical names. To unmerge these groups, delete the entire dynamic group block.
Over time, as your cloud infrastructure changes, the individual groups that make up a dynamic group can end up with no assets. Dynamic groups may end up with no assets, because Tanzu CloudHealth could not find any assets that match the classifcation rule for the dynamic group. This can happen when a tag value used for classifying assets is no longer being used.
To delete all empty groups within a dynamic group, click the broom icon.
You cannot edit classification rules of individual groups in a dynamic group because a dynamic group is governed by a single rule that builds all groups within it.
Tanzu CloudHealth builds perspectives based on classification rules that separate your assets into groups. These rules can be based on any asset data available in your environment, such as Amazon tags or Chef environment. Here’s a semantic example of one such rule:
In the typical workflow, you define classification rules through the Search or Categorize approach and these rules create groups. After defining a group, you can change the underlying rule to fine-tune the assets that are gathered into that group.
After you set the parameters of the group:
not yet updated
mode.pending
.not yet updated
status is cleared and the pending
status is removed from all reports.When you configure a cloud provider account in the Tanzu CloudHealth Platform, you need to provide the platform read-only access to query your cloud provider for changes in asset inventory.
Changes in your asset inventory are monitored through API queries to the cloud provider that collect inventory metadata on assets and their tags. Depending on the asset, these queries are queued at different frequencies such as 15 min, 1 h, 4 h, and 24 h. However, these frequencies are not the intervals at which the Tanzu CloudHealth platform refreshes with changes in your cloud asset inventory. Factors such as network latency, the number of queued items to be processed, the number of services that you utilize, and service-level rate limits determine how quickly the query responses are returned to the Tanzu CloudHealth Platform.
Cloud assets that you terminated or deleted from your cloud provider are removed from the Tanzu CloudHealth Platform 12 months from the date of termination or deletion.
As Tanzu CloudHealth discovers new assets in your cloud infrastructure and changes to existing assets, these changes are reflected in the Perspectives you configured in the Tanzu CloudHealth Platform.
It can take up to 3 h from when new assets are discovered for them to be included in your Perspectives. During the phase of discovery, you will not be able to use Group Filters to find new assets in Perspective Groups.
Tanzu CloudHealth reports are not affected as much by changes in infrastructure. This is because Tanzu CloudHealth reports reflect a lag of 12-24 h from changes in your infrastructure. Any changes you make today, should reflect in Tanzu CloudHealth reports in 12-24 h.
The Tanzu CloudHealth Platform regularly synchronizes reports with changes you make to your Perspectives.
Here are a few changes that the Tanzu CloudHealth Platform monitors for and synchronizes between Perspectives and reports.
When a Perspective is modified, the status indicator next to the name of the Perspective cycles through the following states:
In addition, individual reports in the platform have a dropdown at the bottom of the page that indicates the synchronization status of various Perspectives with that report.
The Tanzu CloudHealth Platform classifies AWS service costs for reporting, Perspective-based grouping, and analytics in one of the following ways:
Line items for these costs in the AWS Detailed Billing Report or Cost and Usage Report must contain a resource ID in order for them to be mapped to a specific asset. Tanzu CloudHealth can attribute these costs to a specific asset and can therefore directly allocate them to a Perspective Group. Tanzu CloudHealth supports these assets in one of these ways:
Line items for these costs in the AWS Detailed Billing Report or Cost and Usage Report may or may not contain a resource ID. If Tanzu CloudHealth does not provide basic cost allocation and asset reporting for this asset and the line item does not contain tags matching those used in any Perspective Group, then the Tanzu CloudHealth platform cannot directly attribute these costs to a Perspective Group. However, you can indirectly attribute these costs to a specific Perspective Group using Cost Reallocation Rules.
Organize line item costs in your AWS bill into common service categories. Differentiate between types of costs, for example, determine how S3 costs are split between storage, API calls, and data transfer.
The Indirect Cost Management level supports all services and assets not supported at the Basic Cost Allocation or Asset Reporting levels.
Prerequisites None.
Service Support
Organize line item costs in your AWS bill into common service categories. Cost from line items with tags present in the bill that match tags used in Perspective Groups will directly be allocated to the Perspective Group. Costs from line items with no matching tags can still be directly allocated to Perspective Groups by either using custom tags or assigning those costs directly in the Perspective Group editor.
For more information, see AWS documentation on Using Cost Allocation Tags.
Services Supported at This Level
Prerequisites
To support the derivation of asset and tag data from the CUR, you must configure the AWS Account to include Cost Allocation Tags in the CUR artifacts. Tanzu CloudHealth recommends adding each tag key that you are using for perspective grouping as a Cost Allocation Tag. To know how you can tag services in your bill, see Configure Cost Allocation Tags.
Service Support
Impact of This Level
Why did cost allocation for an asset in Tanzu CloudHealth reports change when support for it moved from Indirect Cost Management to Basic Cost Allocation? When the approach of allocating costs by the bill was rolled out, the Tanzu CloudHealth Platform recalculated historical costs (for the past 13 months) for all AWS services that were previously marked as Indirect Costs in reports. Because the new allocation is based on tags, any tag-based Perspectives that you had built in the Tanzu CloudHealth Platform now carry costs for more AWS services. Consequently, the allocation of costs likely looks different in your Tanzu CloudHealth reports.
How to leverage assets supported for the Basic Cost Allocation level in the Tanzu CloudHealth Platform?
What happens when assets are deleted and recreated with the same resource ID? In the Tanzu CloudHealth Platform, assets are unique by the resource ID attributed to them in the Detailed Billing Report or the Cost and Usage Report. When an asset is deleted and then later recreated with the same resource ID, Tanzu CloudHealth will consider the recreated asset to be the same as the original asset.
What happens when the tag on an asset changes? The latest key-value pair of a tag trumps all previous key-value pairs of the same tag. When a tag changes, Tanzu CloudHealth changes the asset allocation to whichever Perspective Group is associated with the new tag value. Let’s consider a more complex example. Consider that the Tanzu CloudHealth Platform reads the bill in September 2016 and captures a tag X
for a service item. Then, Tanzu CloudHealth reads an older bill from, say, January 2016 (because AWS placed a new bill due to adjustments) and finds an older tag Y
for the same service item. Now, the service item is tagged with tag Y
until Tanzu CloudHealth reads the bill again in 12-24 hours, at which point tag X
trumps tag Y
once again.
Costs are directly associated with assets collected and processed from the AWS API and reported in an Asset Report. You can assign assets into Perspective Groups via all meaningful attributes of the assets.
Services Supported at This Level:
Prerequisites:
Service Support: All support covered by previous level, plus: