Verify your collectors have env attributes

Before you can target specific environments with a pipeline, each collector must have an env attribute set. In this milestone, you’ll check whether your collectors already have env values, and add them in bulk if they don’t.

If you’ve completed the Categorize a collector fleet learning path, your env attributes are already set — the first section is a quick verification check.

You must have administrator privileges to complete this learning path.

  1. Click the Inventory tab.

  2. Check the Attributes column. If your collectors already show env values, you’re done with this section and can skip ahead to the next milestone. If any collectors are missing env values, continue with the steps below to add the attribute.

  1. Select the collectors you want to tag by checking their checkboxes.

  2. Click Edit remote attributes to open the bulk edit dialog.

  3. In the dialog, click Add remote attributes to expand and complete the form:

    1. In the Key field, type env.

    2. In the Value field, type the environment name, for example dev.

    3. Click Apply changes to save the attribute to all selected collectors.

  4. Repeat the selection and assignment for each environment group, using values such as staging, prod-eu, and prod-us according to your deployment strategy. Once your collectors are tagged and ready, Fleet Management can use the env attribute to target specific environments when assigning pipelines.

In the next milestone, you’ll roll out a pipeline to your development environment first.


page 3 of 7