influxdata / influxdata/telegraf
input support k8s events
Open
Nobody has claimed this yet.
feature request
- Dominant language
- Go
- Stars
- 17.8k
- Forks
- 5.8k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 161
Description
### Use Case
want to use telegraf to collect k8s events into kafka
### Expected behavior
we can use telegraf collect k8s events to other platforms
### Actual behavior
inorder to analyse k8s events
### Additional info
_No response_
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
The issue names no files, tests, or entry points. Start by locating Telegraf's Kubernetes input and Kafka output entry points, then clarify the event data and destination behavior; completion criteria and tests are not specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kafka, kubernetes
- Domain
- devops, observability, stream-processing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100