AsperforMias opened a new pull request, #1155:
URL: https://github.com/apache/dubbo-go-samples/pull/1155

   ## Summary
   
   Extend the existing observability example with repeatable capture of raw 
metrics, OTLP spans and context logs. Validate both sides' counts, trace fields 
and parent IDs, and CtxLogger output with valid, absent and invalid contexts.
   
   Use a non-empty group/version and pin the SDK to merged commit 
`e4aabaf27773`; the previous pin includes the group/version in `rpc.service`. 
Other dependency versions stay unchanged.
   
   Refs apache/dubbo-go#3767.
   
   ## Validation
   
   - Five actual CLIENT/SERVER pairs; both sides record 5 requests, 4 successes 
and 1 business failure. Trace parent IDs, error status and context logs are 
checked.
   - Nine offline checks pass, including malformed captures. Integration Go 
tests and the existing helper race tests pass.
   - The checked-in capture preserves a runtime mismatch: consumer 
`service.name` identifies the client, but metric `application_name` identifies 
the provider. The strict check exits 1 and reports it. Admin pages were not 
tested.
   
   With a temporary module replacement pointing to runtime commit `b2e79b0f`, 
the same live capture passes every strict check, including consumer application 
alignment.
   
   The runtime fix is 
[apache/dubbo-go#3770](https://github.com/apache/dubbo-go/pull/3770). An 
unmerged runtime checkout is used only for additional acceptance testing; this 
PR does not reference that branch or change its SDK behavior. The consumer 
field alignment still needs that fix to merge and an SDK pin update.
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to