Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
处理了链路追踪使用zipkin时的3个问题:
1.requesterFactory之前试图替换为hyperf的httpClientFactory。但是没有生效。
2.zipkin上报后,服务端的响应可以是200,也可以是202,但是目前限制死了只能为202,导致每次服务端正确响应后,都new 了一个Runtime异常。我查看了openzipkin/zipkin-go客户端,它允许服务端响应状态码为200~299。 从实际出发,阿里云、火山云的链路追踪,上报后的http状态码是200而不是202。
3.创建http上报对象时,传入了logger类,便于发生了Runtime异常时定位原因