标签是一种键值对，可分配给 Google Cloud 实例。它们可以帮助您按照所需的粒度大规模组织这些资源并管理费用。您可以将标签附加到各项资源，然后根据其标签对资源进行过滤。标签的相关信息会转发到结算系统，以便您按标签细分结算费用。借助内置的结算报告，您可以按资源标签对费用进行过滤和分组。您还可以使用标签查询结算数据导出。
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-09-04。"],[[["\u003cp\u003eLabels in Bigtable are key-value pairs that allow you to group related instances and store metadata, enabling you to organize resources and manage costs.\u003c/p\u003e\n"],["\u003cp\u003eEach Bigtable resource can have up to 64 labels, each with keys and values that must adhere to specific length and character requirements, and keys must be unique within each instance.\u003c/p\u003e\n"],["\u003cp\u003eCommon uses for labels include categorizing instances by team, component, environment, state, and ownership, helping with cost accounting and resource management.\u003c/p\u003e\n"],["\u003cp\u003eLabels can be added, updated, and removed via the Google Cloud console, RPC Admin API, or REST Admin API, providing flexible management options.\u003c/p\u003e\n"],["\u003cp\u003eWhile labels serve as queryable annotations, they cannot set policy conditions, in which case tags should be used instead, as they provide more fine-grained control.\u003c/p\u003e\n"]]],[],null,["Create and manage instance labels\n\nBigtable provides the option to add labels to your instances. Labels are\nkey-value pairs that you can use to group related instances and store metadata\nabout an instance.\n\nThis page explains how you can use labels with your Bigtable\ninstances. It also describes how to add, update, and remove the labels for an\ninstance.\n\nWhat are labels?\n\nA label is a key-value pair that you can assign to Google Cloud instances.\nThey help you organize these resources and manage your costs at scale, with the\ngranularity you need. You can attach a label to each resource, then filter the\nresources based on their labels. Information about labels is forwarded to the billing system that\nlets you break down your billed charges by label. With built-in [billing reports](/billing/docs/how-to/reports),\nyou can filter and group costs by resource labels. You can also use labels to\nquery [billing data exports](/billing/docs/how-to/bq-examples).\n\nRequirements for labels\n\nThe labels applied to a resource must meet the following\nrequirements:\n\n- Each resource can have up to 64 labels.\n- Each label must be a key-value pair.\n- Keys have a minimum length of 1 character and a maximum length of 63 characters, and cannot be empty. Values can be empty, and have a maximum length of 63 characters.\n- Keys and values can contain only lowercase letters, numeric characters, underscores, and dashes. All characters must use UTF-8 encoding, and international characters are allowed. Keys must start with a lowercase letter or international character.\n- The key portion of a label must be unique within a single resource. However, you can use the same key with multiple resources.\n\nThese limits apply to the key and value for each label, and to the\nindividual Google Cloud resources that have labels. There\nis no limit on how many labels you can apply across all resources\nwithin a project.\n\nCommon uses of labels\n\nHere are some common use cases for labels:\n\n- **Team or cost center labels** : Add labels based on team or\n cost center to distinguish instances owned by different\n teams (for example, `team:research` and `team:analytics`). You can use this\n type of label for cost accounting or budgeting.\n\n- **Component labels** : For example, `component:redis`,\n `component:frontend`, `component:ingest`, and `component:dashboard`.\n\n- **Environment or stage labels** : For example,\n `environment:production` and `environment:test`.\n\n- **State labels** : For example, `state:active`,\n `state:readytodelete`, and `state:archive`.\n\n- **Ownership labels** : Used to identify the teams that are\n responsible for operations, for example: `team:shopping-cart`.\n\n\n| **Note:** Don't include sensitive information in labels, including personally identifiable information, such as an individual's name or title. Labels are not designed to handle sensitive information.\n\nWe don't recommend creating large numbers of unique labels, such as\nfor timestamps or individual values for every API call.\nThe problem with this approach is that when the values change frequently or with\nkeys that clutter the catalog, this makes it difficult to effectively filter and\nreport on resources.\n\nLabels and tags\n\nLabels can be used as queryable annotations for resources, but can't be used\nto set conditions on policies. Tags provide a way to conditionally allow or\ndeny policies based on whether a resource has a specific tag, by providing fine-grained\ncontrol over policies. For more information, see the\n[Tags overview](/resource-manager/docs/tags/tags-overview).\n\nAdd or updating an instance's labels\n\nAfter you [create a Bigtable instance](/bigtable/docs/creating-instance), you can\nuse the Google Cloud console to add labels to the instance and update existing\nlabels. You can also use the [RPC Admin API](/bigtable/docs/reference/admin/rpc) or the [REST Admin\nAPI](/bigtable/docs/reference/admin/rest) to add or update labels.\n\nTo add or update labels for a Bigtable instance using the\nGoogle Cloud console:\n\n1.\n Open the list of Bigtable instances in the Google Cloud console.\n\n\n [Open the instance list](https://console.cloud.google.com/bigtable/instances)\n2. Check the box next to each instance whose labels you want to modify.\n\n3. If the **Labels** panel is not visible, click **Show info panel** in the\n upper right corner to open it.\n\n4. Add and update labels as needed.\n\n To add a new label, click **Add label**, then type the key and value for the\n label.\n\n To modify an existing label, update its value. You cannot change the key for\n an existing label.\n5. Click **Save** to save your changes.\n\nRemove a label from an instance\n\nTo remove a label from a Bigtable instance using the\nGoogle Cloud console:\n\n1.\n Open the list of Bigtable instances in the Google Cloud console.\n\n\n [Open the instance list](https://console.cloud.google.com/bigtable/instances)\n2. Check the box next to each instance whose labels you want to remove.\n\n3. If the **Labels** panel is not visible, click **Show info panel** in the\n upper right corner to open it.\n\n4. Click the X next to each label that you want to remove.\n\n5. Click **Save** to save your changes.\n\nWhat's next\n\n- Learn how to [modify other properties of a Bigtable\n instance](/bigtable/docs/modifying-instance).\n- View per-instance Bigtable usage in the [Cloud Billing\n detailed export to BigQuery](/billing/docs/how-to/export-data-bigquery-tables/detailed-usage)."]]
