Configuration Management
Note
This is a public preview feature intended for use in development environments only. Not recommended for production use.
The Configurations tab displays all configuration groups, where each group represents a configuration and its complete version history. For every group, you can view its status, description, last activation time, and who modified it. You can also review the agents affected by the configuration and control whether a version is active and applied. Select a configuration group to expand it and view all of its versions and their status.
Configuration group
A configuration group contains all versions of a configuration and shows the overall state of those versions.
- Group status reflects the strongest status among all versions. Status priority is: active → inactive → draft.
- A group becomes active as soon as any agent reports an active status for one of its versions.
- Active (!) indicates failures on one or more agents.
- Active (yellow) indicates pending updates—some agents have not yet applied the configuration.
- A group remains applying until at least one agent reports a final status.
Note
If you deactivate a configuration while it is still applying, some agents may receive the configuration and others may not. To avoid inconsistent states, do not deactivate during rollout. Instead, roll back to another version so all agents align on the same configuration.
Configuration family
A configuration family contains several interdependent configurations that must be deployed together. Use configuration families when changes to one component also require updates to other components, like gateways or agents, to keep the system in sync. Learn more about configuration behavior in our Configuration deep dive guide.
Manage configuration versions
Each configuration group contains one or more versions. Versions are immutable snapshots of both the configuration YAML and the agent selector. A new version is created whenever either of these changes.
When a new version is created
A new version is created only when you perform one of the following actions:
- You edit the configuration YAML.
- You modify the agent selector.
- You clone an existing version, which always creates a new configuration group.
- You reactivate a version. Reactivating creates a new clone of the currently active version and sets it as the active version.
- You activate an inactive version. Activating an inactive version creates a new version and makes it active.
Group actions
- Group actions are available only for the active version in the configuration group.
- If there is no active version, group actions apply to the latest version in the group.
Available version actions
| Action | Description |
|---|---|
| Edit | Opens the version for modification. Saving changes creates a new version. |
| Clone | Creates a new version based on the selected one, duplicating both its YAML and agent selector. |
| Activate | Makes the selected version active for all agents matching its selector. Only one version per group can be active at a time. Does not create a new version unless changes were made. |
| Deactivate | Marks the version as inactive. Agents previously using it receive a no-operation configuration and fall back to a minimal supervisor-managed configuration. |
| Reactivate | Available for active versions. Creates a new version and immediately activates it. |
Priority across configuration groups
The order of configuration groups determines version precedence. If multiple configuration groups apply to the same agent, the active version of the highest-ranked group in the list takes priority. You can reorder configuration groups to adjust their priority.
Create a new configuration
To create a new configuration, select the + New configuration button to open the New configuration modal.
- Enter a name and, optionally, a description for your configuration.
- Use the Agent selector's interactive builder to choose agents that will be affected by this configuration using specific attributes.
- In the Configuration field, enter configuration content or upload a YAML file.
- The Preview section on the side displays a list of all agents that match the selection and a summary of their health and status.
- Review the configuration and agent list, then select Create.
Note: The Name, Agent selector, and Configuration fields are required.
Edit an existing configuration
- Hover over a configuration row and select the edit icon .
- In the configuration modal, make any required changes. The Preview panel updates automatically to show which agents are affected.
You can also choose a different configuration version to edit.
Review configuration changes
When you save changes to an existing configuration, a diff view appears so you can review the modifications before applying them. The diff highlights added, removed, and modified lines, allowing you to verify exactly what will change in the new configuration.
Saving changes creates a new configuration version. Existing versions remain available for comparison and rollback. You can compare versions, search within them, and choose whether to activate a new version immediately or keep it inactive.
Permissions
To manage remote configurations in Fleet Management, you must have the proper permissions.
Access can be granted in two ways:
Assign an admin role (Legacy Admin, Organization Admin, or Data Admin), which automatically provides full Fleet Management permissions.
Grant explicit remote configuration permissions using the FleetManagement permission preset or an individual permission.
Preset Action Description FleetManagement REMOTE-CONFIGURATION:MANAGEManage remote configurations (create, edit, activate, deactivate)
Limitations
Each configuration group supports up to 10 configurations. Contact Support if your environment requires a higher limit.