redpanda-data / redpanda-data/connect
Add metadata fields for messages from socket_server input
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.8k
- Forks
- 969
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 64
Description
I have many tcp clients connect to the same socket on the machine runs the redpanda connect, and many operations I want to perform is client-based, such as:
- sending back heartbeat messages
- grouping
- deduplication
- redirecting
It would be useful to fill the metadata fields of the messages received by socket_server, using the information from different network layer, for example, source IPs from the IP layer and ports from transport layer. Other inofrmation can be useful to others but not for my use case, such as the source MAC address from the data link layer.
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 locating the socket_server input implementation and the existing message metadata handling. Determine which network-layer values can be exposed for received messages, then verify that messages from multiple clients carry the expected source information and that the behavior is covered by the relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking, stream-processing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100