Skip to content

Document how standalone Elastic Agent input settings map to Beats options - #7734

Draft
bmorelli25 wants to merge 2 commits into
mainfrom
docs-135-standalone-agent-config
Draft

Document how standalone Elastic Agent input settings map to Beats options#7734
bmorelli25 wants to merge 2 commits into
mainfrom
docs-135-standalone-agent-config

Conversation

@bmorelli25

@bmorelli25 bmorelli25 commented Aug 4, 2026

Copy link
Copy Markdown
Member

Fixes #7794.

The issue listed five problems. One is already fixed: elastic-agent-inputs-list.md provides the list of supported inputs. This PR covers the rest.

Background: standalone Agent passes input settings through to the underlying Beat unchanged, apart from type, id, use_output, log_level, and policy.revision. That's documented in the agent repo (docs/agent-policy.md) but not in the Fleet docs, so there was no way to know that settings like period and cpu.metrics are valid in elastic-agent.yml.

Changes:

  • elastic-agent-input-configuration.md: new "Find the settings available for an input" section with the passthrough rule, the reserved field table, and an example setting period and cpu.metrics on a stream.
  • configure-standalone-elastic-agents.md: new minimum configuration section (one output, one input).
  • beats-agent-comparison.md: the Modules row linked only to Filebeat, implying Metricbeat modules weren't supported. Now links both. Also removed two stale "9.0.0-beta1" qualifiers; version references elsewhere in the repo are at 9.4.0.

Two things I need confirmed:

  • The minimum config omits data_stream.namespace. I couldn't confirm from source that it defaults to default. If it's required, the example needs that line.
  • data_stream.type is not documented here. I couldn't find where it gets set (not in agent-policy.md or component-specs.md).

…ions

Standalone users had no way to discover settings like period or cpu.metrics
that appear in Fleet-exported configs. Agent passes input settings through to
the underlying collector unchanged apart from a few reserved fields, but that
rule was never stated in the Fleet docs, so finding available options required
guesswork.

Adds the passthrough rule and the reserved field list, a minimum viable
standalone config, and points the Modules comparison row at Metricbeat as well
as Filebeat. Also drops two stale 9.0.0-beta1 version qualifiers.

Co-authored-by: Cursor <cursoragent@cursor.com>
@bmorelli25
bmorelli25 requested a review from a team as a code owner August 4, 2026 20:42
@github-actions

github-actions Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Elastic Docs AI PR menu

Check the box to run an AI review for this pull request.

Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

@bmorelli25
bmorelli25 marked this pull request as draft August 4, 2026 20:43
@github-actions

github-actions Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

@github-actions

github-actions Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

✅ Elastic Docs Style Checker (Vale)

No issues found on modified lines!


The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.

This comment was marked as outdated.

@github-actions github-actions Bot left a comment

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.

Docs review summary

Focus areas

  • Style and clarity: Mostly clean; two Vale wordiness suggestions ("in order to" → "to", "not possible" → "impossible") in unchanged/pre-existing lines — not blocking. New prose is clear and follows active voice/second person conventions.
  • Jargon: No unexplained Elastic-internal jargon introduced in the new sections.
  • Frontmatter and applies_to: No frontmatter changes in this PR; Vale's mapped_pages warning is pre-existing/unrelated to the diff.
  • Content type fit: New sections fit the how-to/reference structure of the surrounding pages.
  • Parent issue satisfaction: Partially satisfied. The linked issue (elastic/ingest-docs#135) lists five gaps; this PR is explicit that it addresses the remaining four but leaves two open questions unresolved (data_stream.namespace default behavior, and where data_stream.type gets documented) — flagged with inline comments where they map to specific lines. PR is marked draft, consistent with these open items.

Notes

  • The PR author explicitly calls out two unconfirmed technical claims in the description; I've added inline comments on the corresponding lines so they're visible during review rather than restating them only here.

Generated by Docs review agent for #7734 · sonnet50 · 35 AIC · ⌖ 6.47 AIC · ⊞ 15.6K

Comment thread reference/fleet/elastic-agent-input-configuration.md Outdated
Comment thread reference/fleet/configure-standalone-elastic-agents.md
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
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.

Doc: Elastic Agent standalone documentation can use improvements

2 participants