elastic / elastic/integrations

[docs-patrol] Update filestream config text for logs.ecs stream

Open
#18,003 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Handlebars
Stars
333
Forks
647
Avg merge
2d 17h
Merged PRs (30d)
225

Description

Recent code changes introduced documentation drift in the filestream package manifest.

## Changes Requiring Documentation Updates

### 1. Filestream setting now targets `logs.ecs`, but two descriptions still reference `logs`

**Commit(s):** `87ca21c0ec4aa3e8191ea0c49dad3022f3ab4c71` (`Use the \`logs.ecs\` index instead of \`logs\``)

**What changed:**
- `packages/filestream/agent/input/filestream.yml.hbs` changed from `index: logs` to `index: logs.ecs`.
- `packages/filestream/manifest.yml` updated the setting title/description to `"logs.ecs" data stream`.

**Documentation impact:**
In `packages/filestream/manifest.yml`, two user-facing descriptions are still stale and reference the old stream name:
- `packages/filestream/manifest.yml:53` — `This field is ignored when 'Use the "logs" data stream' is enabled` (for `data_stream.dataset`)
- `packages/filestream/manifest.yml:61` — `This field is ignored when 'Use the "logs" data stream' is enabled` (for `pipeline`)

These should reference `"logs.ecs"` for consistency with current behavior and the updated `use_logs_stream` setting text.

## Suggested Actions

- [ ] Update `packages/filestream/manifest.yml` line text in the `data_stream.dataset` description to say `Use the "logs.ecs" data stream`.
- [ ] Update `packages/filestream/manifest.yml` line text in the `pipeline` description to say `Use the "logs.ecs" data stream`.
- [ ] Verify package docs/rendered UI strings consistently use `logs.ecs` for this setting.

---
[What is this?](https://ela.st/github-ai-tools) | [From workflow: Docs Patrol](https://github.com/elastic/integrations/actions/runs/23484171673)

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.
> - [x] expires on Mar 31, 2026, 10:24 AM UTC

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.