[Improve][SDK] Update message metrics when no available worker in the DataProxy Go SDK
- Dominant language
- Java
- Stars
- 1.5k
- Forks
- 572
- Avg merge
- 22h 7m
- Merged PRs (30d)
- 8
Description
### Description
In the Dataproxy Go SDK, messages rejected with ErrNoAvailableWorker in Send/SendAsync are not reflected in the message metrics, so these failures are invisible in monitoring.
### InLong Component
InLong SDK
### Are you willing to submit PR?
- [x] Yes, I am willing to submit a PR!
### Code of Conduct
- [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
Contributor guide
Research direction
Start in the DataProxy Go SDK at the Send and SendAsync entry points, and trace how ErrNoAvailableWorker is handled. Compare those failure paths with existing message-metric updates; done means rejected messages are represented in the metrics for both synchronous and asynchronous sends.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100