VOOZH about

URL: https://docs.datadoghq.com/agent/fleet_automation/configure_integrations/

⇱ Configure Agent Integrations

For AI agents: A markdown version of this page is available at https://docs.datadoghq.com/agent/fleet_automation/configure_integrations.md. A documentation index is available at /llms.txt.

Configure Agent Integrations

Fleet Automation can deploy, update, and remove integration configuration files (conf.d) on your Agents remotely. Select target Agents by host or tag, choose an integration, and Fleet Automation pushes the configuration change across your fleet.

Prerequisites

  • Remote Configuration enabled for your organization
  • Agent version 7.76 or later
  • Linux VMs (installed with the install script or the Ansible Datadog Role) or Windows VMs
Configuring integrations on Agents in containerized workloads is not supported.

Compatibility

Fleet Automation supports configuring out-of-the-box integrations that have a conf.d configuration file, such as Redis, MySQL, and Windows Certificate Store.

Custom checks are not supported.

Configure integrations across multiple Agents

As you step through the configuration wizard, the Configuration Summary panel shows your current selected scope of Agents. Use this to check how a change would affect an Agent by previewing configuration diffs on a specific Agent in scope.

  1. In Fleet Automation, open the Configuration tab and click Configure Agents.

  2. Scope the configuration to the target Agents. Filter by host information or tags to target a specific group.

  3. Choose Agent integrations.

  4. Select the integration to configure.

    Fleet Automation can detect unconfigured integrations on your hosts. If a process is running on a host that has an available Datadog integration but no active configuration, it appears in the list of Unconfigured integrations detected on your hosts. Use this to identify monitoring gaps across your fleet.

  5. Select an operation (see How configuration changes are applied for more information about each operation):

    • Add New. Specify the filename for the new configuration file, and fill in the configuration as prompted.
    • Edit & Replace. Click Select a file and choose the configuration file you want to replace, then fill in the new configuration as prompted.
    • Delete. Click Select a File to Delete.
    Toggle between Visual and YAML mode when filling out the integration configuration. Use YAML mode to paste in YAML directly.

  6. Review the deployment plan. Fleet Automation generates a configuration diff for each affected Agent so you can verify the exact changes.

  7. Click Deploy Configuration to start the deployment. Track progress from the Deployments page.

How configuration changes are applied

Each operation applies changes to the integration’s conf.d configuration file differently:

  • Add New: Deploys a new integration configuration file. If a configuration file already exists, it is replaced entirely and the YAML you provide becomes the complete new configuration for that integration on the target Agents.

  • Edit & Replace: Only the fields you specify are modified; unmentioned fields remain unchanged.

    Array fields (such as tags) are fully replaced during an Edit & Replace, not merged. Include all desired values in your update. Any values you omit are removed.

  • Delete: Removes the integration configuration file from the target Agents.

Further Reading