_on_error() static function that I really want to treat as public, as I have a need to log exceptions already handled further down and reported via a callback as just the Python exception object.
Hi all,
As the doc https://www.jaegertracing.io/docs/1.19/troubleshooting/ says "The logging reporter follows the sampling decision made by the sampler, meaning that if the span is logged, it should also reach the agent or collector."
But thats not happening, my gRPC server is logging the span - "{"level":"info","msg":"Reporting span 1559209397c51d88:3217766e13b74f76:1559209397c51d88:1","time":"2020-11-11T17:31:47Z"}" , but I am not able to see the same span jaeger-all-in-one UI.
The REST client span is projected onto the UI and is the parent of the trace.
Please help me to be able to project the grpc spans onto UI.
1 reply
is there anyone who could publish a release of the fix in this issue? opentracing-contrib/javascript-express#16
the last update from Austin was
Lemme figure out who has the creds to release this, but yeah, we can get it out
and that was in August
Capturing request data involves privacy risks, so it's not supported by the standard instrumentation. But you're free to add some custom instrumentation and record additional data into the spans.
Is there a class which we need to extend for custom implementation any quick pointers or documentation should help us
I was thinking of building a wrapper for ScopeManger that keeps track of the wall clock time that a span spends active to approximate how many cpu time has been spent on a span (including children). I am intending this to be used in concert with making the span inactive. The ultimate goal is to use this as a vehicle for resource quotas.
Has anyone done this already?
Hi! Is it possible to inherit parent span's tags?
Your spans should inherit the "baggage" https://opentracing.io/docs/overview/tags-logs-baggage/ which travels with the SpanContext between your services. Tags aren't sent but are easily identifiable when you look at the whole trace, so depending on the tools you're using to consume the traces, you may be able to easily visualise the parent Span's tags, e.g. in Jaeger its quite easy to expand the parent span
I am a college graduate from India.
I am here for the project "Performance comparison between OpenTelemetry and OpenTracing instrumentation libraries" For the Outreachy Summer internship program.
I am a newbie here. I'll be grateful if any of you can help me to get started
Some context for ☝️: added the opentracing agent instead of the opentelemery agent to a react frontend (communicating with a dotnet backend with an otel tracer).
need to determine if switching to opentelemetry and redoing auto. and manual instrumentation would be easier than trying to get opentracing agent to always use w3c headers.
