Magento CRON Job Names are missing in NewRelic: "Transaction Names"

[PiotrSiejczuk]

Preconditions (*)

1. Magento 2.1.x or 2.2.x or 2.3.x OpenSource / Commerce / Cloud
2. Correctly Configured Magento CRON Jobs
3. Issue Details: Transactions named /index.php or /unknown

Steps to reproduce (*)

1. Any Magento CRON Job Executed via Standard Scheduler
2. Any Magento CRON Job Executed via CLI Command
3. Check NewRelic APM Monitoring - Transactions. Check below Screenshot to see the unwanted situation:

Expected result (*)

1. NewRelic APM showing exact CRON Job Code as Names within Transaction Traces
2. Number of unknown transaction percentage should get reduced
3. Improved Trace-ability of Transactions for Performance Review Operations

Above screen has 2 transactions "hidden" with white box and red border due to project specific names and data that cannot be desclousered

Actual result (*)

1. NewRelic shows unknown transaction in Transaction Traces

[m2-assistant]

Hi @PiotrSiejczuk. 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-engcom-team give me 2.3-develop instance - upcoming 2.3.x release

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

@PiotrSiejczuk do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

[lbajsarowicz]

I think that's great issue for tomorrow Magento Contribution Day with @magento/strix

Extra information:
https://docs.newrelic.com/docs/agents/php-agent/troubleshooting/transactions-named-indexphp-or-unknown

[PiotrSiejczuk]

@lbajsarowicz that is indeed the idea for this ticket :) Will pick it up and hopefully fix it in a few hours :)

[lbajsarowicz]

Question to @PiotrSiejczuk and @maghamed - what should be the depth of the NewRelic descriptions:

I've done some PoC

[lbajsarowicz]

Created PR #22059 for CLI commands.

I'm not sure if we can achieve something that @PiotrSiejczuk asked, as usually Cron Jobs are ran in groups and I'm not sure if one PHP execution can contain multiple transactions. So that... I just added transaction name based on CLI command name.

I'm doing investigation if we can have multiple transactions in one runtime.

[PiotrSiejczuk]

I am an old school guy, so, there is a Patch for normal CRON Flows:

patch -p0 < Magento2.3.x-NewRelicCRONTransactionTrackingPatch.patch

Magento2.3.x-NewRelicCRONTransactionTrackingPatch.zip

I am going to create a PR in a few moment too

[m2-assistant]

Hi @engcom-backlog-nazar. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 6. Add label Issue: Confirmed once verification is complete.

• 7. Make sure that automatic system confirms that report has been added to the backlog.