[Bug]: recursive tracing in all-in-one #4657
Description
What happened?
Steps to reproduce
- run all-in-one
- reload screen a few times
- observe above trace
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