[DOCS-14295] Add configuring Agent integrations to Fleet Automation docs#37105
[DOCS-14295] Add configuring Agent integrations to Fleet Automation docs#37105evazorro wants to merge 7 commits into
Conversation
|
/review |
There was a problem hiding this comment.
🤖 Automated review by Claude. AI-generated; verify before acting.
One blocker (an unresolved (tk) placeholder in the Delete operation instructions) plus a couple of small consistency/wording nits. Recommend resolving the placeholder before merge.
Reviewed 57a088138f7f142714129e4a653d68bbe1b32db8 — workflow run
Preview links (active after the
|
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
|
|
||
| Custom checks are **not** supported. | ||
|
|
||
| ## Configure integrations across multiple Agents |
There was a problem hiding this comment.
I'm not currently mentioning the Summary side panel in this procedure (the right-side thing that gives you a running configuration summary as you click through the wizard). Is there anything we want to mention about it?
|
|
||
| - {{< ui >}}Add New{{< /ui >}}: 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. | ||
|
|
||
| - {{< ui >}}Edit & Replace{{< /ui >}}: Applies a targeted change using JSON Merge Patch ([RFC 7386][5]). Only the fields you specify are modified; unmentioned fields remain unchanged. |
There was a problem hiding this comment.
Is it important for users to know that it uses this JSON merge patch RFC? It was in the ticket you filed, @ethandebnath7702, so I included it, but personally I would leave it out. Seems like an implementation detail to me.
|
|
||
| <div class="alert alert-info">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 <strong>Unconfigured integrations detected on your hosts</strong>. Use this to identify monitoring gaps across your fleet.</div> | ||
|
|
||
| 1. Select an operation (see [How configuration changes are applied](#how-configuration-changes-are-applied) for more information about each operation): |
There was a problem hiding this comment.
I'm opting to have the details in a separate section rather than inline in the procedure because then we can link to that section if needed (e.g. if Support gets a question about the different options).
What does this PR do? What is the motivation?
Adds a new doc on how to configure Agent integrations via Fleet Automation. This feature has been available in Preview for a little while and is currently undocumented.
Merge instructions
Merge readiness:
AI assistance
Wrote the draft myself, used Claude Code to hook it up to navigation and to suggest rewording in a few places.
Additional notes