Skip to content
This repository was archived by the owner on Apr 28, 2022. It is now read-only.

Ignore Jaeger internal traces in HttpSender (#154) #156

Merged
merged 1 commit into from
Aug 25, 2019
Merged

Ignore Jaeger internal traces in HttpSender (#154) #156

merged 1 commit into from
Aug 25, 2019

Conversation

bocharovf
Copy link
Contributor

Which problem is this PR solving?

Resolves #154

Short description of the changes

Mark Jaeger client internal requests made by HttpSender with "ot-ignore" property which prevents requests from being instrumented by OpenTracing.Contrib.NetCore package.

Ignore Jaeger internal traces in HttpSender.

Mark Jaeger client internal requests made by HttpSender with
"ot-ignore" property which prevents requests from being instrumented by
OpenTracing.Contrib.NetCore package and hides them in UI.

Signed-off-by: Philipp Bocharov <bocharovf@gmail.com>
@Falco20019
Copy link
Collaborator

Thanks for fixing it. I currently have only little time.

@Falco20019 Falco20019 added this to the v0.3.4 milestone Aug 25, 2019
@Falco20019 Falco20019 merged commit 6878891 into jaegertracing:master Aug 25, 2019
@Falco20019
Copy link
Collaborator

I just released it as 0.3.4 to NuGET, so that your problem gets fixed quickly.

pull bot referenced this pull request in scope-demo/jaeger-client-csharp Aug 25, 2019
Ignore Jaeger internal traces in HttpSender.

Mark Jaeger client internal requests made by HttpSender with
"ot-ignore" property which prevents requests from being instrumented by
OpenTracing.Contrib.NetCore package and hides them in UI.

Signed-off-by: Philipp Bocharov <bocharovf@gmail.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Infinite span creation for Jaeger internal requests when OpenTracing.Contrib.NetCore and HttpSender are used
2 participants