The Wayback Machine - https://web.archive.org/web/20220311172606/https://github.com/topics/distributed-tracing
Skip to content
#

distributed-tracing

Here are 368 public repositories matching this topic...

pocki
pocki commented Nov 29, 2021

Requirement - what kind of business use case are you trying to solve?

Actual the windows executables (jaeger-agent.exe, jaeger-collector.exe, ...) don't have a version set. It is hard to identify the current used version and check if the actual used version is outdated.

image

Probl

help wanted good first issue
signoz
pranay01
pranay01 commented Mar 7, 2022

Bug description

Header in Top Endpoint section overflows in browser with reduced width

Expected behavior

Header shouldn't overflow

How to reproduce

  1. Go to SigNoz dashboard metrics page with reduced browser window width
  2. Open any application
  3. Top Endpoint panel header appears overflowing

Version information

  • Signoz version: v0.7.1
  • *Browser version
bug good first issue help wanted frontend
transmittable-thread-local

📌 TransmittableThreadLocal (TTL), the missing Java™ std lib(simple & 0-dependency) for framework/middleware, provide an enhanced InheritableThreadLocal that transmits values between threads even using thread pooling components.
  • Updated Mar 9, 2022
  • Java
cijothomas
cijothomas commented Mar 10, 2022

image

It looks like a good amount of time is spent on nuget restore. And majority of them from the example projects, which are not required for all the build/test pipelines. We may benefit, if examples are built in a dedicated pipeline, and ignored by other pipelines.

help wanted good first issue infra
dyladan
dyladan commented Jan 4, 2022

There was an issue in opentracing to add a scope manager, but it doesn't look like it was ever implemented opentracing/opentracing-javascript#112

What is our action item here? Should we just document on the shim that there is no scope manager so we have no shim for it?

_Originally posted by @dyladan in https://github.com/open-telemetry/opentelemetry-specification/is

good first issue up-for-grabs document never-stale
plajjan
plajjan commented Jul 2, 2021

It seems to me that UTC is selected for on the wire representation of time as well as in the database (jaegertracing/jaeger#712), which sort of makes sense, at least with a somewhat naive handling of timezones. However, I think that the Jaeger UI should support displaying times in the timezone local to the user, i.e. of the browser as to reduce the mental load when viewing

codefromthecrypt
codefromthecrypt commented Mar 26, 2019

@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

Improve this page

Add a description, image, and links to the distributed-tracing topic page so that developers can more easily learn about it.

Curate this topic

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."

Learn more