Copy as Markdown[Open in ChatGPT](https://chatgpt.com/?q=Read%20https%3A%2F%2Fcoralogix.com%2Fdocs%2Fuser-guides%2Ffleet-management%2Fautomations.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)[Open in Claude](https://claude.ai/new?q=Read%20https%3A%2F%2Fcoralogix.com%2Fdocs%2Fuser-guides%2Ffleet-management%2Fautomations.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.) # Automate configuration changes across your fleet Automations let you roll out a configuration change to many agents at once. Instead of editing each configuration group by hand, you define one reusable rule that overlays your change onto every group you target, and you can turn it on or off across your whole fleet from a single place. Use it to apply a shared change, such as reducing log verbosity in production or adjusting sampling per environment, in seconds and keep large fleets consistent. Early access Automations is available to early-access customers. To request access, contact your account representative or Coralogix Support. [![The Automations tab in Fleet Management, showing coverage stats and the list of automations](/docs/assets/images/automations-list-7a10df1e71438929925938e91173d197.webp)](https://coralogix.com/docs/assets/images/automations-list-7a10df1e71438929925938e91173d197.webp) ## What you need[​](#what-you-need "Direct link to What you need") * The Fleet Management manage permission (`REMOTE-CONFIGURATION:MANAGE`). See [Permissions](https://coralogix.com/docs/user-guides/fleet-management/permissions.md). * Access to Fleet Management in Coralogix. * At least one configuration group to target. See [Configuration management](https://coralogix.com/docs/user-guides/fleet-management/configuration-management.md). * For a preset-based automation, the target groups must also be preset-based. See [Limitations](#limitations). ## How automations work[​](#how-automations-work "Direct link to How automations work") An automation is a reusable rule that holds a small piece of configuration, called an overlay. When the automation is active, Coralogix deep-merges that overlay onto the current configuration of every group you target. Nothing is copied into each group by hand: the overlay is layered on top of the existing configuration, and you can toggle it on or off at any time. Each automation has: * A **Name** and a **Description**. * A **Type**: **Kubernetes** or **Custom**. * One or more **Target groups**: the configuration groups the overlay applies to. * A **Configuration**: the overlay itself, authored with **Presets** or as **Code** (YAML). * A **Status**: **Active** (applied) or **Inactive** (not applied). ### How the overlay merges[​](#how-the-overlay-merges "Direct link to How the overlay merges") * **Objects merge key by key.** Existing keys are updated and new keys are added. Set a key to `null` to remove it. * **Lists merge with type-aware logic**, not a blind append. Processor order is preserved where it matters, and tail-sampling policies are matched by `name` and updated in place rather than duplicated. * **When several automations target the same group**, the highest-priority automation wins for each setting. You set the order in the Automations table. ## The Automations tab[​](#the-automations-tab "Direct link to The Automations tab") Open **Fleet Management**, then select the **Automations** tab. The cards at the top summarize your fleet: * **Total automations**: how many automations exist, split into active and inactive. * **Type breakdown**: how many are Kubernetes and how many are Custom. * **Fleet coverage**: how many configuration groups have at least one active automation, out of your total groups. * **Uncovered groups**: groups with no active automation. Select **View groups** to list them. The table lists every automation with its **Status**, **Type**, **Target groups**, **Created by**, and **Created at**. Use **Search automations** or **Filtered by** to narrow the list by **Status**, **Type**, **Target group**, or **Created by**. [![Filtering the automations list by status, type, target group, or creator](/docs/assets/images/automations-filter-438e9d1d6a52005696ded28ab28b4219.webp)](https://coralogix.com/docs/assets/images/automations-filter-438e9d1d6a52005696ded28ab28b4219.webp) ## Create an automation[​](#create-an-automation "Direct link to Create an automation") 1. On the **Automations** tab, select **New automation**. 2. Under **Details**, enter a **Name** and a **Description** that explains what the automation changes. 3. Under **Type**, choose **Kubernetes** or **Custom**. 4. Under **Target**, select the **target groups** the overlay applies to. Each group shows how many configs it contains. 5. Under **Configuration**, define the overlay: * Select **Presets** to build it from predefined options, or * Select **Code** to write the overlay directly in YAML. 6. Use the **Preview** panel to confirm the result before you save. See [Preview the impact](#preview-the-impact). 7. Select **Save changes**. [![The Edit automation dialog with Details, Type, Target groups, and the YAML overlay, next to a live YAML preview of the merged result](/docs/assets/images/edit-automation-yaml-6a1766b2be82c0712a8574f0d889ca20.webp)](https://coralogix.com/docs/assets/images/edit-automation-yaml-6a1766b2be82c0712a8574f0d889ca20.webp) The example above overlays a `batch` processor and a `resource/env` attribute onto the targeted Kubernetes groups. The **Preview** shows the full configuration each group receives once the overlay is merged. ## Preview the impact[​](#preview-the-impact "Direct link to Preview the impact") The **Preview** panel shows a live preview of how the overlay changes the targeted group configurations before you save. Switch between three views: * **Config Navigator**: a structured, navigable view of the merged configuration. * **YAML Config**: the full merged YAML. * **Visual Builder**: a visual pipeline view of the merged configuration, with the automation's changes highlighted. [![The Edit automation dialog with the Visual Builder preview, showing the traces, metrics, and logs pipelines](/docs/assets/images/edit-automation-visual-builder-1684632d8927b3a342f2d192189ad8da.webp)](https://coralogix.com/docs/assets/images/edit-automation-visual-builder-1684632d8927b3a342f2d192189ad8da.webp) The **Visual Builder** renders each telemetry pipeline (traces, metrics, and logs) as a flow of receivers, processors, and exporters, so you can see exactly where the overlay inserts or changes a component. Drag components from the left panel to build or adjust the pipeline, then select **Apply to YAML**. [![The Visual Builder canvas with the traces, metrics, and logs pipelines and the component palette](/docs/assets/images/visual-builder-108b1fcf377a1d22dcc20dcc9757715f.webp)](https://coralogix.com/docs/assets/images/visual-builder-108b1fcf377a1d22dcc20dcc9757715f.webp) ## Activate or deactivate an automation[​](#activate-or-deactivate-an-automation "Direct link to Activate or deactivate an automation") An automation applies to its target groups only while it is **Active**. * **Activate** an automation to merge its overlay into every target group. The affected configuration version is marked as sourced from the automation. * **Deactivate** it to remove the overlay and restore the previous configuration. Because activation and deactivation apply to every target group at once, you can roll a change out, or roll it back, for your whole fleet in a single action. ## Limitations[​](#limitations "Direct link to Limitations") * The **OpAMP extension** cannot be defined or removed through an automation. * A **preset-based automation** can only merge onto preset-based configurations. Preset values carry agent identity, such as the cluster name, so a preset overlay cannot render against a non-preset configuration. * The **Visual Builder is not available in Safari**. Use Chrome, the Config Navigator, or the YAML editor. * **Scheduled, time-based automations** are not available in the first release. ## Troubleshooting[​](#troubleshooting "Direct link to Troubleshooting") **A configuration shows it was changed by an automation, but no one edited it.** An active automation is overlaying that group. Open the automation from the group's source link and deactivate it to restore the previous configuration. **My sampling rate is much lower than expected after adding a sampling automation.** Tail-sampling policies merge by name, and stacking probabilistic policies multiplies their rates (10% of 10% is 1%). Review the merged result in the **Preview** panel. **My preset-based automation produced an empty or invalid configuration.** The target configuration is not preset-based. Target only preset-based configuration groups. **The Visual Builder button is missing or disabled.** You are in Safari, or the configuration is in Presets mode. Use Chrome, and switch the configuration to Code mode to use the Visual Builder. ## Related resources[​](#related-resources "Direct link to Related resources") * [Configuration management](https://coralogix.com/docs/user-guides/fleet-management/configuration-management.md) * [Configuration templates](https://coralogix.com/docs/user-guides/fleet-management/configuration-templates.md) * [Configuration deep dive](https://coralogix.com/docs/user-guides/fleet-management/configuration-deep-dive.md) * [Permissions](https://coralogix.com/docs/user-guides/fleet-management/permissions.md)