distributed-tracing
Here are 254 public repositories matching this topic...
-
Updated
Oct 6, 2020 - Java
Requirement - what kind of business use case are you trying to solve?
High availability and resiliency of Jaeger in production environments
Problem - what in Jaeger blocks you from solving the requirement?
Currently, the official images for jaeger are on docker hub. Unless one has a docker paid account, image pulls will be rate-limited and pulls may fail at run-time, causing infrastr
-
Updated
Oct 7, 2020 - Java
-
Updated
Oct 6, 2020 - Kotlin
-
Updated
Oct 1, 2020 - Java
-
Updated
Oct 7, 2020 - Go
-
Updated
Oct 7, 2020 - Java
-
Updated
Oct 6, 2020 - Scala
-
Updated
Sep 7, 2020 - C#
-
Updated
Oct 7, 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 8, 2020 - Go
-
Updated
Oct 8, 2020 - C#
-
Updated
Sep 29, 2020 - Java
-
Updated
Sep 25, 2020 - Java
-
Updated
Jul 1, 2020 - Java
-
Updated
Oct 8, 2020 - Vue
Describe the bug
When the trace is older than 2-3 days Jaeger will find traces when you search via the Jaeger UI - when you navigate to the individual trace it successfully loads however if you refresh the page you see this :
To Reproduce
Steps to reproduce the behavior:
- Log a trace
- Wait 3 days
- Search for traces older th
The current getting started guide assumes the user will be starting using the SDK building block packages like tracing, node, and metrics. In the future, it is expected most users will use the SDK package as a starting point and it would be better for the getting started guide to reflect that.
-
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 8, 2020 - C#
-
Updated
Jun 9, 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