Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nested async call Tree is not fully exposed #181

Open
rornfdlek opened this issue Mar 18, 2024 · 2 comments
Open

Nested async call Tree is not fully exposed #181

rornfdlek opened this issue Mar 18, 2024 · 2 comments

Comments

@rornfdlek
Copy link

rornfdlek commented Mar 18, 2024

Hello,
Would it be possible to support a call tree for nested async calls as shown below?
(aysnc call in async call)
MicrosoftTeams-image

Currently the call tree is not fully exposed but just showing first async call only like below capture.
MicrosoftTeams-image (1)

When testing with the latest version, 0.9.0 agent, it seems that this feature is not supported.
(envionment1 : nextjs + trpc module, node 18.18.2)
(envionment2 : nextjs + axios module, node 16.20.0)

Is it possible to develop and support this feature in the future?
I would appreciate your response.

Thank you.

@feelform
Copy link
Collaborator

feelform commented Mar 20, 2024

@rornfdlek
When the NodeJS runtime run with await aync function , The NodeJS runtimes return a promise value of parent function. and then runs other async function.

The case you shared is one that I have not tested. I'll try to validate it in v1.0 and improve it so that it can be traced properly if it is traceable.

Thank you for your excellent task

@rornfdlek
Copy link
Author

Hello, thank you for your kind response.
Could you please let me know approximately when v1.0 will be released?
I'd like to prepare for it and follow up as soon as possible upon confirmation of the schedule.
Thank you for your understanding.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants