Configuration management

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.

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

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.

1. Enter a name and, optionally, a description for your configuration.
2. Use the Agent selector's interactive builder to choose agents that will be affected by this configuration using specific attributes.
3. In the Configuration field, enter configuration content or upload a YAML file.
4. The Preview section on the side displays a list of all agents that match the selection and a summary of their health and status.
5. Review the configuration and agent list, then select Create.

Note: The Name, Agent selector, and Configuration fields are required.

Edit an existing configuration

1. Hover over a configuration row and select the edit icon .
2. In the configuration modal, make any required changes. The Preview panel updates automatically to show which agents are affected.

3. 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 in a draft state.

Compare configuration versions

Use View difference to compare two versions of a configuration group.

To access Compare mode, hover over a configuration group, click :coralogix-actions-more-small:, and select View difference.

You can open View difference from these locations:

• From the configurations tab: open the group version actions menu, then select View difference.
• From an expanded configuration group: select View difference.
• From the YAML editor: open the actions menu, then select View difference.

In the diff drawer:

• Use the version selectors to choose the base version on the left and the comparison version on the right.
• Switch between Configuration and Agent selector to compare different content.
• If the configuration includes multiple configuration types, select the type you want to compare, such as Agent, Cluster, or Gateway.
• Optional: Select Show only differences to hide unchanged lines.
• Use search to find keys or sections in either version.

Archive configurations

Archive configuration groups and families you no longer need to keep your workspace clean and reduce the risk of selecting the wrong configuration. Archiving hides items from the default view while preserving their full history for audit and compliance purposes.

The default view hides archived configurations using a State != Archived filter. The actions menu on each configuration group provides the Archive option.

Archive a configuration family

1. In Coralogix, navigate to Integrations, then Fleet Management, then Configurations.
2. Expand the configuration group containing the family you want to archive.
3. Deactivate the family if it is currently active. Active families cannot be archived.
4. Select the actions menu (⋮) on the family row, then select Archive.
5. Confirm the archive action in the dialog.

The family is removed from the default view. It cannot be reactivated after archiving.

Archive a configuration group

1. Navigate to the Configurations tab.
2. Deactivate all families in the group. A group can only be archived when none of its families are active.
3. Select the actions menu (⋮) on the group row, then select Archive.
4. Confirm the archive action in the dialog.

Archiving a group also archives all families within it. Archived groups appear at the bottom of the configuration list.

View archived configurations

Archived groups and families are hidden from the default view by a State != Archived filter. To view them:

• Remove the State != Archived filter chip from the filter bar, or
• Replace the filter with a state selector that explicitly includes Archived.

With either option, archived items appear alongside active ones, with the State column showing Archived.

Reuse an archived configuration

Archived configurations cannot be reactivated, but you can clone them to create a new configuration based on the archived version. Select the actions menu (⋮) on the archived configuration, then select Clone. This creates a new configuration with the same YAML and agent selector.

Archive rules and constraints

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:MANAGE	Manage remote configurations (create, edit, activate, deactivate, archive)

Limitations

• Each configuration group supports up to 10 configurations. Contact Support if your environment requires a higher limit.
• Archiving is irreversible—archived configurations cannot be restored or reactivated. Clone an archived configuration to reuse it.