Google Projects configured in the VMware Tanzu CloudHealth Platform are assigned a Status that indicates the health of the project. A project can switch between the following statuses depending on specific conditions.
One or more of these errors occurred.
One or more of these errors occurred.
This status only appears for projects that are not consolidated under another project.
All standalone projects enabled in the Tanzu CloudHealth Platform require you to configure a P12 private key and passphrase or a JSON private key. The status Not Configured appears if one of these errors occur.
This status appears in the narrow timeframe between project creation and project verification. Verification occurs each time a new project is enabled or an existing project is updated in the Tanzu CloudHealth Platform. If project verification fails, the Pending state persists.
A catch-all state that appears when conditions do not match those for any of the other states.
Invite users to Tanzu CloudHealth to allow them access to the Tanzu CloudHealth platform.
For BigQuery Billing Export, the costs at resource level is an aggregate of the project, product SKU, and label combination. Tanzu CloudHealth provides visibility using project level labels and perspective engines. In addition to this, labelling at resource level provides better granularity.
The Cost Allocation by Resource Level Label (CARLL) in Tanzu CloudHealth allows users to allocate costs in Perspectives based on the labels that have been added at the resource level. This supports accurate chargebacks/showbacks based on usage at a resource level. Resource level visibility also supports daily granularity.
By default, Tanzu CloudHealth reallocates the unknown billing account cost among all the projects under a given billing account according to the proportion of their original cost. With the Disable GCP Non-project cost reallocation option, you can stop the default billing account cost reallocation and keep that cost under Unknown Projects
at the billing account level.
This feature gives you the flexibility to manage cost reallocation on your own as per your business requirement and build your best chargeback and show back models.
If you disable the cost reallocation of unidentified projects, it won’t be applied to historical data, and the feature does not support backfilling or adjustment.
To disable the automatic cost reallocation, go to Setup > Admin > Settings. Scroll down to the Settings section and turn ON the toggle button.
Toggle | Cost Reallocation |
---|---|
ON | Disabled |
OFF | Enabled |
The frequencies specified below indicate the rates at which Tanzu CloudHealth adds API service queries to a queue. These queries help Tanzu CloudHealth identify changes in your GCP infrastructure. These frequencies are not the intervals at which the Tanzu CloudHealth platform refreshes with changes in your GCP infrastructure.
Tanzu CloudHealth makes the best effort to queue up query requests at these frequencies. However, factors such as network latency, the number of queued items to be processed, the number of GCP services that you utilize, and GCP service-level rate limits determine how quickly the query responses are returned to the Tanzu CloudHealth platform.
A new public region will be discovered automatically and added to the Tanzu CloudHealth platform in 24 to 48 hours. Once discovered, data of the new region and supported assets in that region will be available in the Tanzu CloudHealth platform in approximately 24 hours.
-GKE Clusters
Templates such as Deployment Manager for GCP can be configured to receive notifications for hyperscaler changes. These templates use scripts for creating and enabling the required resources for generating and routing the related events.
Tanzu CloudHealth supports detailed GCP data export for the following resources:
This is now supported only through FlexReports. For resource level visibility, configure detailed data export at the GCP console and configure these for Tanzu CloudHealth GCP accounts.
Note: You can have only one table configured at a time. It is not recommended to change the configuration from detailed export to standard export for an existing account as it will take away all resource level details and Perspectives built on these. These Perspectives will appear as assets not allocated.
Partners can also use existing data-connect API to modify the detailed export table.
Execute the cloud shell script within a GCP project to set up an event stream.
While the event stream is active, you will see real-time updates in the service for any changes in your GCP project.
Execute the cloud shell script within a GCP project to disable and tear down the event stream setup for the added GCP projects.
This script will remove all earlier constructs and will disable event generation on any changes.