---
title: "Designing your attribute schema | Grafana Labs"
description: "How to choose the right attributes for your fleet"
---

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

## How to choose your attributes

Ask yourself: **“What groups of collectors should receive the same configuration?”**

| If you want to target…            | You need an attribute like… |
|-----------------------------------|-----------------------------|
| All production servers            | `env=production`            |
| Collectors in specific regions    | `region=us-east`            |
| Collectors owned by a team        | `team=platform`             |
| Collectors for a specific service | `service=api-gateway`       |

[Start with one question](fleet-management-attribute-schema.svg "Start with one question")

## Common attribute patterns

| Attribute | Example values                   | Use case                     |
|-----------|----------------------------------|------------------------------|
| `env`     | `production`, `staging`, `dev`   | Environment-specific configs |
| `region`  | `us-east`, `eu-west`, `ap-south` | Region-specific collection   |
| `team`    | `platform`, `backend`, `data`    | Team ownership               |
| `service` | `api`, `web`, `worker`           | Service-specific monitoring  |

> **Start simple.** Begin with `env` and one or two others. Add more as needed.