Slide 4 of 14

Designing your attribute schema

How to choose your attributes

A little planning up front saves a lot of pain later. Start by asking one question: “What groups of collectors should receive the same configuration?”

To match a pipeline to…You need an attribute like…
All production serversenv=production
Collectors in specific regionsregion=us-east
Collectors owned by a teamteam=platform
Collectors for a specific serviceservice=api-gateway
Start with one question

Common attribute patterns

AttributeExample valuesUse case
envproduction, staging, devEnvironment-specific configs
regionus-east, eu-west, ap-southRegion-specific collection
teamplatform, backend, dataTeam ownership
serviceapi, web, workerService-specific monitoring

Start simple. Begin with env and one or two others. Add more as patterns emerge from real usage.

Script

Now that you understand what attributes are, let’s talk about how to design them well. A little planning up front saves a lot of pain later.

Start by asking one question: “What groups of collectors should receive the same configuration?” The answer reveals the attributes needed. If all production servers should get the same metrics config, an env attribute is needed. If different regions have different collection requirements, a region attribute is needed. If teams manage their own collectors, a team attribute is needed.

The table on this slide shows common patterns that work well. Environment is the most common: production, staging, development. Region is useful for organizing collectors by geographic location. Team helps with ownership and accountability. Service identifies what the collector monitors.

Start with these basics. More attributes can be added as patterns emerge from real usage.

/
Previous Next