Attribute matching

Attribute matching is the mechanism that connects pipelines to collectors. When you create a pipeline, you define matchers, which are rules that specify which collectors should receive that pipeline based on their attributes.

Matchers determine which collectors receive a pipeline.

How matchers work

You define…	To target…
`env=production`	All collectors with `env` attribute set to `production`
`region=~"us-.*"`	All collectors in any US region

Matcher syntax

Operator	Meaning	Example
`=`	Equals	`env=production`
`!=`	Not equals	`env!=development`
`=~`	Regex match	`region=~"us-.*"`
`!~`	Regex not match	`team!~"test-.*"`

Matching rule: AND logic

All matchers must match for a collector to receive a pipeline.

Matchers defined	Collector receives pipeline if…
`env=prod`	`env` is `prod`
`env=prod`, `region=us-east`	`env` is `prod` AND `region` is `us-east`

Attribute matching is how you tell Fleet Management which collectors should receive a pipeline. It’s inspired by Prometheus Alertmanager’s matcher syntax, so if you’ve used that before, this will feel familiar.

A matcher has three parts: an attribute name, an operator, and a value. The operators are equals, not equals, regex match, and regex not match. For example, “env equals production” or “region matches us-dash-star.”

When you assign matchers to a pipeline, Fleet Management uses AND logic—all matchers must match for a collector to receive the pipeline. So if you have matchers for env equals production AND region equals us-east, a collector needs both attributes to get that pipeline.

This AND logic is important to understand. It means you can be very precise about which collectors receive a configuration. The more matchers you add, the narrower your targeting becomes.

Attribute matching