Examples

Seeing real configurations makes attributes concrete. These two Alloy examples move from a minimal starting schema to a more complete one for a larger deployment.

Example 1: Minimal starting schema

This example shows the recommended starting point for new Fleet Management users: just two attributes:

Alloy Copy

remotecfg {
    // ... other configuration ...
    
    attributes = {
        "env"  = "production",   // Which environment: production, staging, or dev
        "team" = "platform"      // Who owns this collector
    }
}

What you can match with this schema

• All production collectors → env=production
• All collectors owned by platform team → team=platform
• Production collectors owned by platform → env=production, team=platform

Example 2: Expanded schema for larger deployments

As your fleet grows, you may need more precise matching. This example adds a region attribute:

Alloy Copy

remotecfg {
    // ... other configuration ...
    
    attributes = {
        "env"    = "production",
        "region" = "us-east-1",
        "team"   = "platform"
    }
}

What you can match with this schema

• All US East collectors → region=us-east-1
• Production collectors in US East → env=production, region=us-east-1
• Platform team’s US East production collectors → all three attributes

Both examples define local attributes in the local configuration, but you can also set attributes through the Fleet Management API or the user interface. Notice the naming pattern in each: keys are lowercase with no spaces, and values are short, descriptive strings.

Start simple, expand as needed. Begin with Example 1. Add more attributes when you need that level of matching precision.