asyncio.gather tracing produces nested spans

I’ve got the following code:

import asyncio
import sentry_sdk

async def foo():
    with sentry_sdk.start_span(op="foo"):
        await asyncio.sleep(1)

async def bar():
    with sentry_sdk.start_span(op="bar"):
        await asyncio.sleep(1)

with sentry_sdk.start_span(op="root"):
    await asyncio.gather(foo(), bar(), return_exceptions=True)

I see that bar is nested under foo, and foo is nested under root in the Performance UI.

root
    |- foo
         |- bar

Expected behavior: both foo and bar are nested under root and are on the same level.

root
    |- foo
    |- bar

[untitaker]

yes, our asyncio support is somewhat limited at the moment. As a workaround you can do:

import asyncio
import sentry_sdk

async def foo():
    with sentry_sdk.Hub(sentry_sdk.Hub.current):
        with sentry_sdk.start_span(op="foo"):
            await asyncio.sleep(1)

async def bar():
    with sentry_sdk.Hub(sentry_sdk.Hub.current):
        with sentry_sdk.start_span(op="bar"):
            await asyncio.sleep(1)

with sentry_sdk.start_span(op="root"):
    await asyncio.gather(asyncio.create_task(foo()), asyncio.create_task(bar()), return_exceptions=True)

I am not sure if create_task is strictly necessary or if gather does that for you. If gather already creates independent tasks then we can potentially handle this case transparently.

[antonpirker]

I have now created a reproduction repo: https://github.com/getsentry/minimum_python_async/blob/main/task1.py

And I created a new AsyncioIntegration that produces now this output:

Which is the output we want to have 😃