You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Steps to reproduce
A method polls our database waiting for success. We've tried to add suppression for this because we get many 10s of segments for this polling, but spans still get generated.
ctx = set_value("suppress_instrumentation", True)
with tracer.start_as_current_span("polling", ctx):
tt = time.time()
while timeout is None or float(timeout) > time.time() - tt:
status = cls.status(job_id)
if not status.is_pending():
return
await asyncio.sleep(increment)
Invoking cls.status(job_id) does a mongo query to determine status.
What is the expected behavior?
I expect that the mongo query triggered by the status call doesn't generate a span.
What is the actual behavior?
many 10s of spans are included in the output of the instrumentation.
Additional context
There's a possibility I'm invoking the code wrong here (I'm new to OpenTelemetry), but the implementation for PyMongo doesn't reference the suppression key like other libraries.
The text was updated successfully, but these errors were encountered:
Describe your environment
Steps to reproduce
A method polls our database waiting for success. We've tried to add suppression for this because we get many 10s of segments for this polling, but spans still get generated.
Invoking
cls.status(job_id)
does a mongo query to determine status.What is the expected behavior?
I expect that the mongo query triggered by the status call doesn't generate a span.
What is the actual behavior?
many 10s of spans are included in the output of the instrumentation.
Additional context
There's a possibility I'm invoking the code wrong here (I'm new to OpenTelemetry), but the implementation for PyMongo doesn't reference the suppression key like other libraries.
The text was updated successfully, but these errors were encountered: