Skip to content

[DOCS-15218] Incorporate feedback on Configure Custom Logs page - #38500

Merged
evazorro merged 3 commits into
masterfrom
eva/DOCS-15218-configure-logs-feedback
Jul 30, 2026
Merged

[DOCS-15218] Incorporate feedback on Configure Custom Logs page#38500
evazorro merged 3 commits into
masterfrom
eva/DOCS-15218-configure-logs-feedback

Conversation

@evazorro

@evazorro evazorro commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

What does this PR do? What is the motivation?

Fixes DOCS-15218

Incorporates some post-merge feedback on the new Configure Custom Logs topic from #38049.

  • Added some extra context to the intro
  • Added backlinks for context:
    • Link from a few places to how to upgrade your Agents
    • Link to learn more about what the different log collection fields do
    • In the warning that containerized workflows aren't supported, link to docs on Kubernetes log collection
  • Added steps for verifying that log collection config deploy worked
  • (small) Removed a couple stray </a> tags that I noticed

Merge instructions

Merge readiness:

  • Ready for merge

Additional notes

[RESOLVED - thanks all!] Open questions (cc @ethandebnath7702):

- Does the Agent need a restart after Fleet Automation pushes log configuration, the way the manual conf.d flow does?
- Does a pushed configuration take effect on an Agent that still has logs_enabled: false? If not, log collection belongs in Prerequisites.

Comment thread content/en/agent/fleet_automation/configure_logs.md Outdated
@oleroydatadog

Copy link
Copy Markdown
Contributor
  1. Does the Agent need a restart after Fleet Automation pushes log configuration, the way the manual conf.d flow does?
    OL: It's automatically done.
  2. Does a pushed configuration take effect on an Agent that still has logs_enabled: false? If not, log collection belongs in Prerequisites.
    OL: It's written but it's useless since logs are disabled. It will take effect one logs_enabled: true

- Agent version 7.76 or later
- Agent version 7.76 or later. To upgrade your Agents, see [Upgrade Agents][5].
- Linux VMs (installed with the install script or the Ansible Datadog Role) or Windows VMs
- Log collection enabled on the target Agents (`logs_enabled: true` in `datadog.yaml`). Fleet Automation deploys the configuration file either way, but the Agent does not start collecting logs until log collection is enabled. See [Host Agent Log Collection][8].

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.

@coignetp @oleroydatadog listing this under Prerequisites for thoroughness, but let me know if you think this is unnecessary!

@evazorro
evazorro marked this pull request as ready for review July 29, 2026 15:34
@evazorro
evazorro requested a review from a team as a code owner July 29, 2026 15:34
@evazorro
evazorro requested a review from coignetp July 29, 2026 16:51
@evazorro
evazorro merged commit 7157c02 into master Jul 30, 2026
35 checks passed
@evazorro
evazorro deleted the eva/DOCS-15218-configure-logs-feedback branch July 30, 2026 14:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants