Manage Collector membership

FleetAMP treats Collector membership as a governed change. An administrator or authorized Group Owner can propose which OpenTelemetry Collectors belong to a group, preview the effect, obtain approval when required, and retain immutable evidence.

A Collector can belong to only one ownership group. Labels may narrow deployment targets inside a group, but they do not grant access or change ownership.

Choose a membership method

Method	Best for	How it works
Explicit selection	Stable servers and known Collectors	Select currently unassigned Collectors
Dynamic rule	Short-lived, autoscaled, or frequently rebuilt Collectors	Match stable identity or reported attributes using a wildcard or regular expression
Move	A Collector that belongs in another ownership boundary	Remove it from the source group and assign it to the destination group
Remove	A Collector that should become unassigned	Remove ownership and choose how its active group configuration is handled

Add Collectors while creating a group

1. Open Groups & Labels.
2. Select Create group.
3. Enter the group and ownership details.
4. Choose one or more entries from Available Collectors.
5. Optionally define a dynamic membership rule.
6. Review the resolved membership preview.
7. Create or submit the proposal according to your approval policy.

Already assigned Collectors are not shown as available. Move them through the membership workspace.

Dynamic membership

Rules can evaluate a stable Collector ID, display name, runtime name, host.name, or another reported attribute. Prefer simple wildcards such as payments-prod-collector-*; use regular expressions only when necessary.

FleetAMP rejects enabled ownership rules whose current matches overlap another enabled group.

caution

Use attributes that remain stable across restarts. Kubernetes pod names and generated instance UIDs may change when a workload is recreated.

Removing a dynamically matched Collector creates an explicit exclusion so the rule does not immediately add it back.

Configuration behavior

Policy	Result
Keep current configuration	Membership changes without replacing the current configuration
Restore pre-group configuration	FleetAMP proposes the last known configuration from before group membership
Deploy destination group configuration	The assigned or moved Collector receives an approved version belonging to the destination group

FleetAMP rejects stale membership proposals and configuration versions owned by another group.

Approval, execution, and recovery

1. The requester chooses the operation and configuration policy.
2. FleetAMP resolves eligible Collectors and saves a target snapshot.
3. Preflight validates ownership, authorization, and compatibility.
4. A different eligible reviewer approves the exact proposal when required.
5. Execution updates the recorded targets.
6. Results and audit events remain available for review.

If a later target fails, FleetAMP attempts compensating rollback for earlier successful targets in reverse order. Review any rollback_failed result manually. Per-target outcomes include completed, failed, restored, rollback_failed, and not_started.

Authorization

• Administrators can manage membership across all groups.
• Group Owners can act only within groups they own.
• Moving a Collector requires authority over both source and destination groups.
• Labels never expand group permissions.
• A requester cannot approve their own governed proposal.