distributed-tracing
Here are 262 public repositories matching this topic...
-
Updated
Oct 30, 2020 - Java
Requirement - what kind of business use case are you trying to solve?
Allow people to safely export production traces into GitHub tickets (as a way of reproducing problems, especially with the UI) without exposing sensitive information.
Problem - what in Jaeger blocks you from solving the requirement?
The anonymizer is partially implemented.
Proposal - what do you suggest to s
-
Updated
Oct 30, 2020 - Java
-
Updated
Oct 30, 2020 - Kotlin
-
Updated
Oct 27, 2020 - Java
-
Updated
Oct 29, 2020 - Go
-
Updated
Oct 29, 2020 - Java
-
Updated
Oct 29, 2020 - Scala
-
Updated
Oct 29, 2020 - C#
-
Updated
Oct 28, 2020 - Scala
Flaky code coverage
This coverage change came up in a PR #530 that did not touch the source code at all
It is likely that there is a race condition that makes this line not being executing in some cases. Need to make it more deterministic.
-
Updated
Oct 29, 2020 - C#
-
Updated
Oct 30, 2020 - Go
From #276
Right now tempo-cli is a utility for debugging purposes but there are plans to extend its functionality.
Created this issue to track/discuss the improvements of the tool.
This was brought up in a PR comment by @ThomsonTan.
Currently we don't have a consistent message, here are the options:
- {VariableName} should be {description of the constraint}.
- {VariableName} should be {description of the constraint}, the actual value is {ActualValue}.
Please suggest which one
-
Updated
Oct 30, 2020 - Java
-
Updated
Oct 23, 2020 - Java
-
Updated
Oct 13, 2020 - Java
-
Updated
Oct 27, 2020 - Vue
According to the spec, null attribute values are invalid/undefined behavior. This should be documented.
Update the spec compliance matrix upon completion.
-
Updated
Jun 28, 2020 - Go
@thegryfon noticed that in community axios implementations, some leak contexts and you wouldn't necessarily know until a second root trace is attempted.
here's an example scenario I think tests could cover:
there is no parent trace in scope
create a client request
create a second client request
verify that both client requests are root spans
See: #1482
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
Oct 2, 2020 - Go
-
Updated
Oct 30, 2020 - C#
Improve this page
Add a description, image, and links to the distributed-tracing topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the distributed-tracing topic, visit your repo's landing page and select "manage topics."



Please answer these questions before submitting your issue.
Question
org.springframework.kafka.KafkaListenerEndpointContainer#0-4-C-1 InstMethodsInter : class[class org.postgresql.jdbc.PgPreparedStatement] before method[executeWithFlags] intercept fai