elastic / elastic/elastic-agent
[docs-patrol] Update EDOT components reference for awscloudwatchreceiver
- Dominant language
- Go
- Stars
- 275
- Forks
- 264
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 312
Description
Recent code changes in the repository have introduced documentation drift. The following change needs a corresponding documentation update.
## Changes Requiring Documentation Updates
### 1. EDOT added `awscloudwatchreceiver`, but the public EDOT components reference is missing it
**Commit(s):**
- [`cfd76549e937f49f20c1379c82e0db3180c4ac31`](https://github.com/elastic/elastic-agent/commit/cfd76549e937f49f20c1379c82e0db3180c4ac31)
**What changed:**
- `internal/edot/otelcol/components/default.go:25` adds the `awscloudwatchreceiver` import.
- `internal/edot/otelcol/components/default.go:195` registers `awscloudwatchreceiver.NewFactory()` in the default receiver set.
- `internal/edot/README.md:40` includes `awscloudwatchreceiver` in the EDOT receiver inventory.
**Documentation impact:**
- `docs/reference/edot-collector/components.md:27` states the components table is automatically generated from EDOT source.
- In the receiver table, `docs/reference/edot-collector/components.md:40` lists `apachereceiver` and `:41` immediately lists `awss3receiver`, but there is no `awscloudwatchreceiver` entry.
This leaves the public EDOT components reference out of sync with the actual shipped component set.
## Suggested Actions
- [ ] Update/regenerate `docs/reference/edot-collector/components.md` so the receivers table includes `awscloudwatchreceiver`.
- [ ] Verify the EDOT docs generation inputs are refreshed so future component additions stay in sync.
> [!NOTE]
>
> 🔒 Integrity filter blocked 1 item
>
> The following item were blocked because they don't meet the GitHub integrity level.
>
> - [#14544](https://github.com/elastic/elastic-agent/pull/14544) `search_pull_requests`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
>
> To allow these resources, lower `min-integrity` in your GitHub frontmatter:
>
> ```yaml
> tools:
> github:
> min-integrity: approved # merged | approved | unapproved | none
> ```
>
>
---
[What is this?](https://ela.st/github-ai-tools) | [From workflow: Docs Patrol](https://github.com/elastic/elastic-agent/actions/runs/27147561874)
Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.
> - [x] expires on Jun 15, 2026, 3:26 PM UTC
Contributor guide
Research direction
Start with docs/reference/edot-collector/components.md and its statement that the table is generated from EDOT source, then compare the receiver inventory with internal/edot/otelcol/components/default.go and internal/edot/README.md. Follow the documented generation or refresh process and verify that awscloudwatchreceiver appears in the public receivers table and the inputs remain synchronized.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 82/100