Skip to content

Commit da86bdd

Browse files
committed
update tag pipeline descriptions
1 parent 49e437d commit da86bdd

File tree

2 files changed

+4
-3
lines changed

2 files changed

+4
-3
lines changed

content/en/cloud_cost_management/allocation/_index.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,7 @@ The Allocation section of Cloud Cost Management helps you understand and optimiz
1616
## Key features
1717

1818
{{< whatsnext desc="This section includes the following topics:" >}}
19+
{{< nextlink href="/cloud_cost_management/allocation/tag_pipelines" >}}<u>Tag Pipelines</u>: Standardize and enrich your cost data with consistent tagging. Create rules to fix missing or incorrect tags, alias tag keys, and map multiple tags using reference tables. Proper tagging is essential for accurate cost allocation and enables you to break down spending by team, service, or business unit across all allocation methods.{{< /nextlink >}}
1920
{{< nextlink href="/cloud_cost_management/allocation/container_cost_allocation" >}}<u>Container Cost Allocation</u>: Automatically allocate the costs of your cloud clusters to individual services and workloads. Use cost metrics enriched with tags from pods, nodes, containers, and tasks to visualize container workload cost in the context of your entire cloud bill.{{< /nextlink >}}
2021
{{< nextlink href="/cloud_cost_management/allocation/bigquery" >}}<u>BigQuery Cost Allocation</u>: Allocate BigQuery costs to individual queries, users, and projects to understand your data warehouse spending at a granular level. Track query performance costs, storage costs, and slot utilization across your organization.{{< /nextlink >}}
2122
{{< nextlink href="/cloud_cost_management/allocation/custom_allocation_rules" >}}<u>Custom Allocation Rules</u>: Split and assign shared costs to any available tags using custom rules. Choose from even split, custom percentage, proportional by spend, or dynamic by metric allocation methods to support accurate showback and chargeback across teams, projects, or environments.{{< /nextlink >}}

content/en/cloud_cost_management/allocation/tag_pipelines.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -20,11 +20,11 @@ further_reading:
2020

2121
## Overview
2222

23-
To effectively monitor cloud costs, you need to understand how various services, teams, and products contribute to your overall spending. Tag Pipelines enforce the use of standardized tags across your cloud resources and ensure consistent, accurate cost attribution throughout your organization.
23+
Tags are the foundation for all Cloud Cost Management analysis and allocation. They enable you to break down spending by service, team, project, environment, or any dimension relevant to your business. Tag Pipelines enforce the use of standardized tags across your cloud resources and ensure consistent, accurate cost attribution throughout your organization.
2424

25-
With [Tag Pipelines][1], you can create tag rules to address missing or incorrect tags on your cloud bills. You can also create new inferred tags that align with specific business logic to enhance the accuracy of your cost tracking.
25+
With [Tag Pipelines][1], you can create tag rules to address missing or incorrect tags on your cloud bills. You can also create new inferred tags that align with specific business logic to enhance the accuracy of your cost tracking. These standardized tags power all cost analysis capabilities, including container cost allocation, custom allocation rules, and cost recommendations.
2626

27-
Tag Pipelines apply to Cloud Cost metrics from all providers, affecting both cost data and cost recommendations.
27+
Tag Pipelines apply to Cloud Cost metrics from all providers. The rules you create affect all cost data and cost recommendations, ensuring consistency across dashboards, monitors, and allocation reports.
2828

2929
When tag pipelines change, the new rules are automatically applied to the most recent three months of data. It may take up to 24 hours for the historical data update to complete after rules are added or modified.
3030

0 commit comments

Comments
 (0)