New Relic is not being given useful transaction names for graphql requests

[convenient]

 
{quote}

Description (*)

Every graphql is being given the same transaction name in new relic.

This means when using a PWA site that most of the requests do not get split out in any useful way in New Relic. They all get lumped into /FrontController/Magento\GraphQl\Controller\GraphQl\Interceptor.

This makes it really hard to debug specific slow or buggy requests. I would classify this as a bug because it makes New Relic pretty useless with a Magento PWA stack and makes it much harder to support.

Expected behavior (*)

We have some better naming of transactions within the application. Maybe something like

- /GraphQL-productDetail
- /GraphQL-getCartDetails

There is an open discussion here https://discuss.newrelic.com/t/feature-idea-magento-2-graphql-api-transaction-naming/98824 but both the options discussed there make it seem like this fix needs to come from within the Magento application.

Benefits

Having the transactions properly broken down within New Relic is vital for supporting the application at an enterprise level. It's a big step back to not have this functionality.

Additional information

N/A
{quote}

[m2-assistant]

Hi @convenient. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[sasha19957099]

@magento I am working on this

[nizarn]

@magento export issue to Jira project MC