Magento 2.0.18 is the final 2.0.x release. After March 2018, Magento 2.0.x will no longer receive security patches, quality fixes, or documentation updates.
To maintain your site's performance, security, and PCI compliance, upgrade to the latest version of Magento.

New Relic APM

The software analytics product New Relic for application performance management (APM) helps you to analyze and improve application interactions. Each Magento Commerce Cloud plan includes a New Relic APM license that supports up to three instances across all environments. You do not need to purchase or install the New Relic extension (different than the APM service). For plan details, see Subscriptions and plans.

Key features

New Relic APM provides the following features to Magento:

  • Focus on specific transactions—Actively mark and monitor key customer actions in your site, such as adding to the cart, checking out, or processing a payment.
  • Database query monitoring—Locate and monitor database queries affecting performance.
  • App Map—View all application dependencies within your Magento site, extensions, and external services.
  • Apdex scores—Evaluate performance and create alerts that identify issues and notify you when they occur, such as site performance affected by a flash sale or web event.

New Relic APM credentials

The agent software for New Relic is packaged with your Magento Commerce Cloud account. You receive your credentials and license information from Magento during launch. You can access your license key in the Project Web Interface by clicking View Details for your project. The NewRelic Service section includes your Account Number, License Key, and other access keys.

Add New Relic APM to an environment

The Magento Commerce Cloud plans support up to three instances of your New Relic APM license across all environments. We recommend adding a New Relic license to your staging and production environments, and you can add the license to one other environment of your choice.

If you have more than three active environments using the same New Relic license key, you need to remove a license variable from an existing environment. For details, see Remove New Relic from an environment.

If you are interested in using New Relic on more than three active environments, contact your dedicated Launch Manager for details, or you can contact New Relic directly at sales@newrelic.com.

To add a New Relic license key to an environment:

  1. Open a terminal
  2. Checkout a branch in your local environment.
  3. Set the license variable.

    magento-cloud variable:set --no-visible-build php:newrelic.license <your-new-relic-license-key>
    

Remove New Relic APM from an environment

The Magento Commerce Cloud plans support up to 3 instances of your New Relic license across all environments. If you have more than 3 active environments using the same New Relic license key, you need to remove a license variable from an existing environment.

To remove a New Relic license key from an environment:

  1. Open a terminal
  2. Checkout a branch in your local environment.
  3. List all variables.

    For project variables: magento-cloud pvget
    For environment variables: magento-cloud vget

  4. Delete an environment variable.

    magento-cloud variable:delete php:newrelic.license
    

    If you added the license as a project variable, you must remove that project-level variable. A project variable adds the license to every environment branch created, using or exceeding the license limit.

    magento-cloud project:variable:delete php:newrelic.license
    

Add New Relic extension to your project

New relic extension must be listed in the .magento.app.yaml project file:

runtime:
    extensions:
    - newrelic

Investigate performance

New Relic connects and monitors your site using a PHP agent. As it collects data, you can log in and review the responses through the New Relic dashboard.

Using the New Relic dashboard, you can immediately track and find the following:

  • Monitor applications and transactions encountering slow responses or bottlenecks
  • Investigate customer comments of issues with your site
  • Identify applications with high transaction time and follow up on queries, calls, and methods with Blackfire
  • Verify and compare traffic to transaction time

We recommend reviewing tracked data:

  • Most time consuming—Determine time consumption by tracking requests in parallel. For example, you may have the highest transaction time spent in product and category views. If a customer account page suddenly ranks very high in time consumption, there may be a call or query dragging performance.
  • Highest throughput—Identify pages hit the most based on the size and frequency of bytes transmitted.

All collected data details the time spent on an action transmitting data, queries, or Redis data. If queries cause issues, New Relic provides information to track and respond to it.

New Relic and Blackfire

You can mix the high-level data captured by New Relic APM and the code-level data captured by the Blackfire Profiler to gain insight into your store performance. Each service has strengths and weaknesses that balance incredibly well together.

  • The New Relic worst-case requests are not averages, but edge cases; whereas, Blackfire provides more of the average worst-case requests.
  • Blackfire is not detailed in determining and displaying queries giving you trouble, but you can use New Relic to find those.
  • Background processes, like Cron job, can cause issues. These background processes are not monitored by New Relic, but you can watch them using Blackfire.

New Relic APM resources