opentracing
Here are 477 public repositories matching this topic...
-
Updated
Feb 26, 2021 - Go
-
Updated
Dec 30, 2020 - TypeScript
-
Updated
Aug 4, 2020 - Java
Tracking issue, similar to jaegertracing/jaeger#2645
Done:
- #548
- #549
- #550
Remaining:
- publish crossdock images
- remove .travis.yml
- update build badge in README
- change required checks to new GH jobs
非常感谢大家对 SOFAStack 开源的关注和支持,这是我们前进最大的动力。
收集目的
- 了解 SOFAStack 的使用场景以便更好的规划技术路线
- 聆听社区的不同声音,让 SOFAStack 变得更好
- 吸引更多的开源爱好者参与贡献,共同打造 SOFAStack
收集方式
请按如下参考格式回复本 Issue 进行登记:
* 公司/组织名称:蚂蚁金服
* 地点:中国杭州
* 网址:http://www.antfin.com
* 使用组件及场景:全套金融级分布式中间件
* 联系方式:zhanggeng.zg@antfin.com
展示
我们会定期同步信息至「Awesome SOFA」的用户列表中。
服务
-
Updated
Aug 4, 2020 - C
-
Updated
Apr 23, 2020
Requirement - what kind of business use case are you trying to solve?
Our traces contain data that is covered by GDPR (european user privacy regulations) and, thus developers do not have direct access to all traces. If an error occurs, relevant traces has to be filtered out and the relevant ones are forwarded to the developer.
Another use case:
It would be nice to just attach files with
-
Updated
May 15, 2019 - Java
Cannot use same trace ID accross different node of microservices
On the document of https://opentracing.io/docs/overview/tracers/#propagating-a-trace-with-inject-extract, there is a concept of inject and extract. This is working fine with http carrier. Yet, I cannot reproduce this with Text Map carrier.
Please create a doc for u
-
Updated
Jun 28, 2020 - Go
-
Updated
May 18, 2020 - Java
-
Updated
Feb 5, 2019 - Go
-
Updated
Jan 27, 2021 - Go
-
Updated
Feb 26, 2021 - C++
-
Updated
Oct 14, 2019 - Go
Support for log4j2
I'm using log4j2 in my SpringBoot application, excluding logback implementation and logging with tracer doesn't work. It would be nice to support logging with log4j2 .
-
Updated
Feb 17, 2021 - HCL
-
Updated
Nov 28, 2019 - Go
-
Updated
Jan 22, 2021 - Java
-
Updated
Feb 10, 2021 - C#
-
Updated
Feb 26, 2021 - Scala
-
Updated
Feb 26, 2021 - JavaScript
Improve this page
Add a description, image, and links to the opentracing topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the opentracing topic, visit your repo's landing page and select "manage topics."



As far as I can tell, we are not using it today. The motivation for it was to have a canonical proto-based JSON API that would be used by the UI as well as a public API. But there are issues with proto-based JSON (e.g. IDs are represented in base64 instead of hex)
and updating the UI is a large task that we don't have the cycles for. I suggest we remove this dependency altogether until the time w