---
title: "Attribute telemetry cost by team with Fleet Management | Grafana Labs"
description: "Learn how to add the Fleet Management team attribute to your metrics as a label, and use that label in Cost Management and Billing to attribute Grafana Cloud telemetry cost to teams."
---

> For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt).

# Attribute telemetry cost by team with Fleet Management

Welcome to the Grafana Fleet Management learning path that shows you how to attribute Grafana Cloud telemetry cost to the teams that own your collectors.

The `team` attribute you assign to a collector in Fleet Management describes the collector, not the telemetry it sends. In this path, you use a configuration pipeline to add the `team` attribute to your metrics as a label. Then you use that label in Cost Management and Billing to see how much each team spends.

## Here’s what to expect

When you complete this path, you’ll be able to:

- Explain how a collector attribute becomes an attribution label
- Create a configuration pipeline that adds the `team` label to your metrics
- Confirm that the `team` label appears on your metrics
- Configure `team` as a cost attribution label in Cost Management and Billing
- Review cost by team and find unattributed cost

## Before you begin

Before you attribute cost by team, ensure that you have:

- Grafana Alloy collectors that run on Linux and are registered in Fleet Management. The pipeline in this path collects Linux host metrics.
- The `team` attribute assigned to those collectors in Fleet Management. To assign it, refer to the [Categorize a collector fleet](https://grafana.com/docs/learning-paths/categorize-collector-fleet/) learning path.
- The `GCLOUD_RW_API_KEY` environment variable set on those collectors. The variable holds an access policy token with the `metrics:write` scope.
- The Prometheus remote write URL and username for your stack. Refer to [Find instance endpoints](https://grafana.com/docs/grafana-cloud/security-and-account-management/cloud-stacks/#find-instance-endpoints) for details.
- **Admin** permissions in Grafana Cloud to create configuration pipelines.
- The **Cost attribution admin** role to configure attribution labels. Refer to [Role-based access control for Cost Management and Billing](https://grafana.com/docs/grafana-cloud/cost-management-and-billing/set-up/cost-management-billing-rbac/) for more information.
- The **Cost attribution reader** role to view the attribution report. The **Cost attribution admin** role already includes read access.

## Troubleshooting

If you get stuck, we’ve got your back! Where appropriate, troubleshooting information is just a click away.

## More to explore

We understand you might want to explore other capabilities not strictly on this path. We’ll provide you opportunities where it makes sense.

Are you ready?

[Let's go!](https://grafana.com/docs/learning-paths/attribute-cost-by-team/business-value/)