elastic / elastic/docs-content
Docs about Input in Filebeat is not well structured
- Dominant language
- No language data
- Stars
- 47
- Forks
- 261
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 116
Description
Filebeat documentation seems to not be well structured (kind of a doc bug) for 8.x version.
1. Go to https://www.elastic.co/guide/en/beats/filebeat/8.19/filebeat-module-elasticsearch.html
2. Click on `Configure` --> `Inputs` on the left menu.
3. You will see that on the left menu, under "Inputs", only 4 type of inputs are listed there, where there should be a long list as in the page loaded when going to Inputs (second screenshot bellow):
4. It seems that **part of that list** was wrongly included right after `Configure` -> `Configuration options`
5. The same menu is well structured in 9.x doc
TriageBot — Complete
### 2026-07-02
**Type:** bug
**Section check:**
- ✅ What's broken / actual behavior: Only 4 input types appear under "Configure → Inputs" in the 8.19 left nav; a much longer list is expected (and part of that list is incorrectly placed under "Configure → Configuration options")
- ✅ Expected behavior: Full input list shown in nav, consistent with the 9.x docs
- ✅ Reproduction steps: Direct URL + click path provided with supporting screenshots
**Cross-references:**
- https://www.elastic.co/guide/en/beats/filebeat/8.19/filebeat-module-elasticsearch.html — valid Elastic docs URL (8.x legacy Beats docs)
**Next step:** none — issue is complete
> Generated by [Gh Aw Issue Triage](https://github.com/elastic/docs-content/actions/runs/28614418233) for issue #7190 · 29.7 AIC · ⌖ 7.52 AIC · ⊞ 9.1K · [◷](https://github.com/search?q=repo%3Aelastic%2Fdocs-content+is%3Aissue+%22gh-aw-workflow-call-id%3A+elastic%2Fdocs-content%2Fgh-aw-issue-triage%22&type=issues)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at the Filebeat 8.19 filebeat-module-elasticsearch.html page and compare its Configure → Inputs navigation with the corresponding 9.x documentation shown in the issue. Locate the source for the Inputs and Configuration options navigation, then verify that all input types appear under Inputs and that the menu matches the expected structure.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 70/100