[PR] [INLONG-12201][SDK] Update metrics when no available worker in Dataproxy Go SDK [inlong]

["yfsn666 (via GitHub)" <gi...@apache.org>]

yfsn666 opened a new pull request, #12208:
URL: https://github.com/apache/inlong/pull/12208

   <!-- Prepare a Pull Request
   Change the title of pull request refer to the following example:
     [INLONG-XYZ][Component] Title of the pull request 
   -->
   
   <!-- Specify the issue this pull request going to fix.
   The following *XYZ* should be replaced by the actual [GitHub Issue](https://github.com/apache/inlong/issues) number)-->
   
   Fixes #12201
   
   ### Motivation
   
   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.
   
   ### Modifications
   
   Added `c.metrics.incMessage(workerBusy.getStrCode())` in both the `Send` and `SendAsync` paths when no available worker is found, so these rejections are counted alongside other message outcomes.
   
   ### Verifying this change
   
   *(Please pick either of the following options)*
   
   - [x] This change is a trivial rework/code cleanup without any test coverage.
   
   - [ ] This change is already covered by existing tests, such as:
     *(please describe tests)*
   
   - [ ] This change added tests and can be verified as follows:
   
     *(example:)*
     - *Added integration tests for end-to-end deployment with large payloads (10MB)*
     - *Extended integration test for recovery after broker failure*
   
   ### Documentation
   
     - Does this pull request introduce a new feature? no
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@inlong.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org