Slide 8 of 14

Matching in practice

Common patterns

Because every collector carries its own attributes, you can organize your fleet along whatever dimensions fit: environment, region, team, service, or even Kubernetes namespace.

PatternMatcher examples
Environment-basedenv="production", env="staging"
Region-basedregion="us-east", region="eu-west"
Team-basedteam="platform", team="backend"
Catch-allcollector.os=~".+" (matches all collectors)

Example: Production platform pipeline

Matchers: env=~"prod-.*", team="platform"

This pipeline applies to collectors where:

  • env matches the regex prod-.* AND
  • team equals platform

Limits to know

LimitValue
Matcher length200 characters max (key + operator + value)
Local attributes per collector22 max when polling

These limits are generous for most use cases, but worth knowing as you design your schema.

Script

Now that you understand matcher syntax and AND logic, let’s look at how teams typically use attribute matching in practice.

Because collectors have their own attributes, you have flexibility in how you organize your fleet. Maybe by environment and region. Maybe by team and service. Maybe by Kubernetes namespace.

A common pattern is environment-based matching. Your production collectors get production configs, your staging collectors get staging configs, all from the same Fleet Management instance. Region-based matching works similarly, letting you match collectors by geographic area.

You can also create a catch-all matcher using a regex that matches any value. This is useful for pipelines that should apply to every collector in your fleet.

One thing to watch out for: matchers are limited to 200 characters total including key, value, and operator. And collectors can have at most 22 local attributes when polling for configuration. These limits are generous for most use cases, but worth knowing as you design your attribute schema.

/
Previous Next