redpanda-data / redpanda-data/benthos
Component's path information for custom plugins
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 571
- Forks
- 120
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 18
Description
I've been working on developing a custom processor plugin for Benthos and encountered a scenario where accessing the component path information within the plugin would be incredibly useful. Specifically, I'm interested in retrieving the path similar to how it's represented in Benthos logs (e.g., processors.1.switch.1) for more contextual logging and processing within my plugin.
In a discussion with @Jeffail in Discord, it was suggested that this feature would require adding the component path information to the Resources type to be accessible by custom plugins.
P.S. issue moved from Connect repo
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
Start by tracing the Resources type and the component-path information used for Benthos logs, then follow how custom processor plugins receive Resources. Make the path available to plugins and verify that it matches the logged form, such as processors.1.switch.1.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- stream-processing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100