Add GraphQL New Relic transaction naming

[lewisvoncken]

Description (*)

This pull request implements detailed New Relic transaction naming for GraphQL requests, mirroring the functionality of the JomaShop module. It introduces a new helper and a QueryProcessor plugin to set specific transaction names based on the GraphQL operation type, operation name, and top-level fields. Custom parameters for the number of fields and field names are also added to New Relic.

This change enhances observability by providing more granular and informative transaction data for GraphQL queries and mutations, improving performance monitoring and debugging. The default transaction naming in Magento\GraphQlNewRelic\Model\Query\Logger\NewRelic has been disabled to prevent overwriting the more detailed names set by this new plugin.

Related Pull Requests

Fixed Issues (if relevant)

1. Fixes magento/magento2#<issue_number>

Manual testing scenarios (*)

1. Enable New Relic reporting: Ensure New Relic integration is configured and enabled in your Magento instance.
2. Perform a simple GraphQL query:
   • Example: query { products { total_count } }
   • Verify in New Relic that the transaction name is similar to GraphQL-products.
   • Check for custom parameters: GraphqlNumberOfFields (e.g., 1) and FieldNames (e.g., products).
3. Perform a GraphQL query with an explicit operation name:
   • Example: query MyProducts { products { total_count } }
   • Verify in New Relic that the transaction name is similar to GraphQL-MyProducts.
4. Perform a GraphQL query with multiple top-level fields:
   • Example: query { products { total_count } categories { items { name } } }
   • Verify in New Relic that the transaction name is similar to GraphQL-Multiple.
5. Perform a GraphQL mutation (if applicable):
   • Example: mutation { createCart { cart { id } } }
   • Verify in New Relic that the transaction name reflects the mutation type and operation, e.g., GraphQL-createCart.

Questions or comments

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)

[m2-assistant]

Hi @lewisvoncken. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.
❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names.

Allowed build names are:

1. Database Compare
2. Functional Tests CE
3. Functional Tests EE
4. Functional Tests B2B
5. Integration Tests
6. Magento Health Index
7. Sample Data Tests CE
8. Sample Data Tests EE
9. Sample Data Tests B2B
10. Static Tests
11. Unit Tests
12. WebAPI Tests
13. Semantic Version Checker

You can find more information about the builds here
ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.

---

For more details, review the Code Contributions documentation.
Join Magento Community Engineering Slack and ask your questions in #github channel.