influxdata / influxdata/telegraf
S3 Plugin
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 17.8k
- Forks
- 5.8k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 161
Description
## Feature Request
Opening a feature request kicks off a discussion.
### Proposal:
Input Plugin to pull data using a file-reader pattern from s3 buckets into telegraph.
### Current behavior:
Telegraf cannot natively be configured to consume specific formats of s3 data.
### Desired behavior:
Telegraf can utilize a configurable s3 plugin in order to to consume specific formats of s3 data.
### Use case:
Configure an s3 plugin to consume and parse data from AWS loadbalancer logs stored in an S3 bucket to feed telegraf metrics such as the number of unsuccessful http requests made to a specific loadbalancer.
Next Steps:
If there are no objections, I will open a pull request to start work on supporting this new plugin.
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
No files or tests are named in the issue. Start by reviewing Telegraf's existing input-plugin conventions and the requirements for reading configurable formats from AWS S3; done means a configurable S3 input plugin can consume the specified data formats and feed Telegraf metrics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go
- Domain
- cloud, data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100