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.

Sign up for GitHub

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

Jump to bottom

GraphQL Resolver Trace Names Don't Include Path #520

Open
TimPansino opened this issue Apr 20, 2022 · 2 comments · May be fixed by #737
Open

GraphQL Resolver Trace Names Don't Include Path #520

TimPansino opened this issue Apr 20, 2022 · 2 comments · May be fixed by #737
Labels
bug needs-triage stale

Comments

@TimPansino
Copy link
Contributor

Description

GraphQLResolverTrace does not take field path into account, only field name.

Expected Behavior

https://docs.newrelic.com/docs/apm/agents/python-agent/supported-features/python-graphQL#field-resolver-spans
@stale
Copy link

stale bot commented Jun 19, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@dacevedo12
Copy link

Not stale

@stale stale bot added the stale label Jun 19, 2022
@TimPansino TimPansino linked a pull request Jan 5, 2023 that will close this issue
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug needs-triage stale
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[WIP] Add Path to GraphQLResolverTrace newrelic/newrelic-python-agent
2 participants
@TimPansino @dacevedo12