redpanda-data / redpanda-data/connect
Add input_error metric to redpanda input
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.8k
- Forks
- 969
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 64
Description
Hi all,
The redpanda output has output_error metric exposed when it fails to send data.
For some reason, I don't see equivalent for the redpanda input. You may reproduce issue by configuring input to read from non existing topic, or from topic to which user has no access to. In that case in logs I can see "re-updating due to inner errors: UNKNOWN_TOPIC_OR_PARTITION", but there is no any metric based on which I could determine that something is not working
On the other hand, if I use non-existing topic in the redpanda output, then I get the output_error metric counter increased as expected
Is this missing feature or a bug, or is it by purpose?
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
Compare the redpanda input's error handling with the redpanda output's existing output_error metric, focusing on failures such as UNKNOWN_TOPIC_OR_PARTITION and authorization errors. Trace where the input logs re-updating due to inner errors, then confirm that the input_error counter is exposed and increases for those failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- stream-processing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100