Harmonize redis intput/module/output settings
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 12.7k
- Forks
- 5k
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 370
Description
With 7.7.0 we are introducing support for configuring the redis host via URLs in the output. In Beats we have a Filebeat redis logs input (collect logs, not event stream input), Metricbeat redis module, and the redis output. The different plugins should provide a similar set of settings and connection capabilites (`x=present, -=missing`):
settings | output | FB input | MB module |
| --- | --- | --- | --- |
| redis:// URL | x | - | x |
| rediss:// URL | x | - | - |
| URL options | - | - | x |
| URL db number | - | - | x |
| ssl settings | x | - | - |
| proxy | x | - | - |
| proxy local resolver | x | - | - |
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the Filebeat Redis logs input, Metricbeat Redis module, and Redis output implementations, then compare their connection settings against the issue's matrix. Determine the intended shared capabilities and verify that the three plugins expose the agreed Redis URL, database, TLS, and proxy behavior when the work is complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, redis
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100