|
| 1 | +--- |
| 2 | +title: Configure Custom Logs |
| 3 | +description: "Remotely configure custom log collection at scale with Fleet Automation." |
| 4 | +private: true |
| 5 | +further_reading: |
| 6 | +- link: "/agent/fleet_automation/" |
| 7 | + tag: "Documentation" |
| 8 | + text: "Fleet Automation" |
| 9 | +- link: "/agent/fleet_automation/configure_integrations/" |
| 10 | + tag: "Documentation" |
| 11 | + text: "Configure Agent Integrations" |
| 12 | +- link: "/agent/fleet_automation/configure_agents/" |
| 13 | + tag: "Documentation" |
| 14 | + text: "Configure Agents" |
| 15 | +- link: "/api/latest/fleet-automation/" |
| 16 | + tag: "Documentation" |
| 17 | + text: "Fleet Automation API" |
| 18 | +site_support_id: fleet-automation-standard-features |
| 19 | +--- |
| 20 | + |
| 21 | +Use [Fleet Automation][2] to manage custom log collection settings on your Agents remotely at scale. |
| 22 | + |
| 23 | +## Prerequisites |
| 24 | + |
| 25 | +- [Remote Configuration][1] enabled for your organization |
| 26 | +- Agent version 7.76 or later |
| 27 | +- Linux VMs (installed with the install script or the Ansible Datadog Role) or Windows VMs |
| 28 | + |
| 29 | +<div class="alert alert-info"> |
| 30 | +Configuring custom logs on Agents in containerized workloads is not supported. |
| 31 | +</div> |
| 32 | + |
| 33 | +## Configure custom logs across multiple Agents |
| 34 | + |
| 35 | +<div class="alert alert-tip">As you step through the configuration wizard, the <strong>Configuration Summary</strong> 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.</a></div> |
| 36 | + |
| 37 | +1. In Fleet Automation, open the [{{< ui >}}Configuration{{< /ui >}}][2] tab and click {{< ui >}}Configure Agents{{< /ui >}}. |
| 38 | +1. Scope the configuration to the target Agents. Filter by host information or tags to target a specific group. |
| 39 | +1. Choose {{< ui >}}Custom Logs{{< /ui >}}. |
| 40 | +1. Select an operation (for more information, see [How configuration changes are applied](#how-configuration-changes-are-applied)): |
| 41 | + |
| 42 | + - {{< ui >}}Add New{{< /ui >}}. Specify the filename for the new configuration file, and fill in the configuration as prompted. You can add additional log collection settings by clicking {{< ui >}}+ Add Log Collection{{< /ui >}}. |
| 43 | + - {{< ui >}}Edit & Replace{{< /ui >}}. Click {{< ui >}}Select a File{{< /ui >}} and choose the configuration file you want to replace, then update the log collection settings. |
| 44 | + - {{< ui >}}Delete{{< /ui >}}. Click {{< ui >}}Select a File to Delete{{< /ui >}}. |
| 45 | + |
| 46 | + <div class="alert alert-tip">Toggle between <strong>Visual</strong> and <strong>YAML</strong> mode when filling out the log collection configuration. Use <strong>YAML</strong> mode to paste in YAML directly.</div> |
| 47 | + |
| 48 | +1. Review the deployment plan. Fleet Automation generates a configuration diff for each affected Agent so you can verify the exact changes. |
| 49 | +1. Click {{< ui >}}Deploy Configuration{{< /ui >}} to start the deployment. Track progress from the [Deployments page][3]. |
| 50 | + |
| 51 | +## How configuration changes are applied |
| 52 | + |
| 53 | +Each operation applies changes to custom log collection on an Agent differently: |
| 54 | + |
| 55 | +- {{< ui >}}Add New{{< /ui >}}: Deploys a new configuration file. |
| 56 | + |
| 57 | +- {{< ui >}}Edit & Replace{{< /ui >}}: Replaces the entire configuration file. Include all desired values in your update. Any values you omit are removed. |
| 58 | + |
| 59 | +- {{< ui >}}Delete{{< /ui >}}: Removes the configuration file from the target Agents. |
| 60 | + |
| 61 | +## Further Reading |
| 62 | + |
| 63 | +{{< partial name="whats-next/whats-next.html" >}} |
| 64 | + |
| 65 | +[1]: /agent/guide/setup_remote_config |
| 66 | +[2]: https://app.datadoghq.com/fleet/agent-management |
| 67 | +[3]: https://app.datadoghq.com/fleet/deployments |
0 commit comments