[Issue] Fix - Newrelic GraphQl transaction names not working

[m2-assistant]

This issue is automatically created based on existing pull request: #36436: Fix - Newrelic GraphQl transaction names not working

---

Description (*)

Add transaction names to all new relic graphql transactions.

So many other transactions are properly named without having the newrelicreporting/general/enable=1 flag set.

• cron jobs ( handled by magento php level, so long as the php extension is enabled )
• CLI commands ( handled by magento php level, so long as the php extension is enabled )
• controllers ( handled by new relic agent )
• rest API ( handled by new relic agent)

Currently graphql works like this

• graphql ( handled by magento php level, so long as the php extension is enabled, and the magento extension is enabled with newrelicreporting/general/enable=1 )

Having to enable this new relic reporting module to get GraphQL transaction names seems like a bit of an oversight. It is perfectly viable to have this setup

1. install new relic in the php.ini level, new relic will auto detect that it is magento2

; Setting: newrelic.framework
; Type   : string
; Scope  : per-directory
; Default: empty (auto-detect framework)
; Info   : Disables automatic framework detection, telling the agent to
;          attempt to name transactions according to the specified framework.
;          Specifying "no_framework" will disable framework-related transaction
;          naming entirely. Please let us know at support.newrelic.com if you
;          encounter a failure with framework autodetection.
;
;          Must be one of the following values:
;          cakephp, codeigniter, drupal, drupal8, joomla, kohana, laravel,
;          magento, magento2, mediawiki, silex, slim, symfony1, symfony2,
;          wordpress, yii, zend, zend2, no_framework
;
;          Note that "drupal" covers only Drupal 6 and 7.
;
;newrelic.framework = ""

2. Do not enable the magento extension, set newrelicreporting/general/enable=0
3. Expect to see transaction names for graphql

What we actually see is

/FrontController/Magento\GraphQl\Controller\GraphQl\Interceptor

Related Pull Requests

• Newrelic GraphQl transaction names not working #36112
• New Relic is not being given useful transaction names for graphql requests #30915

Manual testing scenarios (*)

1. Configure new relic in your php.ini
2. Make a graphql request like https://example.com/graphql?luker=3&query=%257Bproducts(filter%253A%257Bsku%253A%257%5B%25E2%2580%25A6%5DA%2522nonsuchsku%2522%257D%257D)%257Bitems%257Bname%2520sku%257D%257D%257D
3. See Graphql-products in your new relic transactions list

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
• All automated tests passed successfully (all builds are green)

[engcom-Alfa]

hey

as per discussion with the internal team confirming the ticket.

[github-jira-sync-bot]

Unfortunately, not enough information was provided to create a Jira ticket. Please make sure you added the following label(s): Reproduced on 2.4.x, ^Area:.*

Once all required labels are present, please add Issue: Confirmed label again.

[github-jira-sync-bot]

✅ Jira issue https://jira.corp.adobe.com/browse/AC-7974 is successfully created for this GitHub issue.

[m2-assistant]

✅ Confirmed by @engcom-Alfa. Thank you for verifying the issue.
Issue Available: @engcom-Alfa, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[engcom-November]

Hi @engcom-Alfa ,
We are closing this issue as this is a duplicate of this ongoing confirmed issue. Kindly move on to this issue for latest updates / solutions on the same.
Thank you.