[Bug]: recursive tracing in all-in-one #4657
Labels
Comments
This was referenced Aug 14, 2023
Merged
yurishkuro
added a commit
that referenced
this issue
Aug 14, 2023
## Which problem is this PR solving? - Resolves #4657 ## Description of the changes - use NoOp tracer provider in the OTLP receiver configuration ## How was this change tested? - ran the UI, reloaded page many times, this endpoint no longer shows up Signed-off-by: Yuri Shkuro <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
Steps to reproduce
Expected behavior
In the past only read queries to the query-service were logged. The span above is the write part, where Jaeger submits tracing spans back to itself. We never instrument the write path as that creates recursive trace collection. We need to exclude the write endpoints from being traced by OTEL instrumentation.
cc @afzal442
Relevant log output
No response
Screenshot
No response
Additional context
No response
Jaeger backend version
No response
SDK
No response
Pipeline
No response
Stogage backend
No response
Operating system
No response
Deployment model
No response
Deployment configs
No response
The text was updated successfully, but these errors were encountered: