Skip to content
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions config/_default/menus/main.en.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -565,16 +565,21 @@ menu:
url: agent/fleet_automation/configure_integrations
parent: agent_fleet_automation
weight: 803
- name: Configure Custom Logs
identifier: configure_logs
url: agent/fleet_automation/configure_logs
parent: agent_fleet_automation
weight: 804
- name: Upgrade Agents
identifier: upgrade_agents
url: agent/fleet_automation/upgrade_agents
parent: agent_fleet_automation
weight: 804
weight: 805
- name: Upgrade SDKs
identifier: upgrade_sdks
url: agent/fleet_automation/upgrade_sdks
parent: agent_fleet_automation
weight: 805
weight: 806
- name: Troubleshooting
url: agent/troubleshooting/
parent: agent
Expand Down
72 changes: 72 additions & 0 deletions content/en/agent/fleet_automation/configure_logs.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,72 @@
---
title: Configure Custom Logs
description: "Remotely configure custom log collection at scale with Fleet Automation."
private: true
further_reading:
- link: "/agent/fleet_automation/"
tag: "Documentation"
text: "Fleet Automation"
- link: "/agent/fleet_automation/configure_integrations/"
tag: "Documentation"
text: "Configure Agent Integrations"
- link: "/agent/fleet_automation/configure_agents/"
tag: "Documentation"
text: "Configure Agents"
- link: "/api/latest/fleet-automation/"
tag: "Documentation"
text: "Fleet Automation API"
site_support_id: fleet-automation-standard-features
---

{{< callout url="#" btn_hidden="true" >}}
Comment thread
evazorro marked this conversation as resolved.
Outdated
Configuring custom log collection with Fleet Automation is in Preview.
{{< /callout >}}

Use [Fleet Automation][2] to manage custom log collection settings on your Agents remotely at scale.

## Prerequisites

- [Remote Configuration][1] 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
Comment thread
evazorro marked this conversation as resolved.

<div class="alert alert-info">
Configuring custom logs on Agents in containerized workloads is not supported.
</div>

## Configure custom logs across multiple Agents

<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>

1. In Fleet Automation, open the [{{< ui >}}Configuration{{< /ui >}}][2] tab and click {{< ui >}}Configure Agents{{< /ui >}}.
1. Scope the configuration to the target Agents. Filter by host information or tags to target a specific group.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it expected to have 1 everywhere instead of 1 2 3 4 ? Same for line 52

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Markdown accepts either -- you can do 1-2-3 or 1-1-1. If the latter, it will automatically number them correctly for you in the built version. I like to do 1-1-1 because then if you insert a step anywhere in the list, you don't have to re-number all the steps that follow.

1. Chose {{< ui >}}Custom Logs{{< /ui >}}.
Comment thread
evazorro marked this conversation as resolved.
Outdated
1. Select an operation (see [How configuration changes are applied](#how-configuration-changes-are-applied) for more information about each operation):
Comment thread
evazorro marked this conversation as resolved.
Outdated

- {{< 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 >}}.
- {{< 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.
- {{< ui >}}Delete{{< /ui >}}. Click {{< ui >}}Select a File to Delete{{< /ui >}}.

<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>

1. Review the deployment plan. Fleet Automation generates a configuration diff for each affected Agent so you can verify the exact changes.
1. Click {{< ui >}}Deploy Configuration{{< /ui >}} to start the deployment. Track progress from the [Deployments page][3].

## How configuration changes are applied

Each operation applies changes to custom log collection on an Agent differently:

- {{< ui >}}Add New{{< /ui >}}: Deploys a new configuration file.
Comment thread
evazorro marked this conversation as resolved.
<!-- what happens if there's an existing config file? is it additive? -->

- {{< ui >}}Edit & Replace{{< /ui >}}: Replaces the entire configuration file. Include all desired values in your update. Any values you omit are removed.
Comment thread
evazorro marked this conversation as resolved.

- {{< ui >}}Delete{{< /ui >}}: Removes the configuration file from the target Agents.

## Further Reading

{{< partial name="whats-next/whats-next.html" >}}

[1]: /agent/guide/setup_remote_config
[2]: https://app.datadoghq.com/fleet/agent-management
[3]: https://app.datadoghq.com/fleet/deployments
Loading