New Relic® Performance Monitoring is a powerful tool for monitoring the performance of a WordPress or Drupal site. It provides insight into how efficiently a website is using resources, and where improvements can be made in the application. Pantheon offers New Relic® Pro within the Site Dashboard on all sites (excluding Basic) for free.
In this guide, we'll automatically label code changes to your site in New Relic®'s Deployment page using Pantheon's Quicksilver hooks and Terminus. This creates a traceable connection between performance changes and code deployments, allowing developers to determine whether a code change positively or negatively impacted performance.
Follow the instructions to activate New Relic® APM Pro if you have not already activated it.
Use Pantheon's Quicksilver hooks to run our example New Relic® script immediately after code is synced on Dev or a Multidev environment and after code is deployed to Test and Live. The script configured in this guide applies a label to the Deployment page in New Relic®.
This process uses Terminus commands that require your site name. Before you begin, set the variable
$sitein your terminal session to match your site name:
Clone your Pantheon site repository if you haven't done so already.
Navigate to the project's root directory. You can use Terminus to provide the clone command:
terminus connection:info $site.dev --fields='Git Command' --format=string git clone ssh://codeserver.dev.2187...email@example.com...d85b.drush.in:2222/~/repository.git sitename
Copy and run the output command and then change directory to the site code root:
Set the connection mode to Git:
terminus connection:set $site.dev git
Create a copy of Pantheon's
new_relic_deploy.phpscript in the project's private path:
mkdir -p private/scripts curl https://raw.githubusercontent.com/pantheon-systems/quicksilver-examples/master/new_relic_deploy/new_relic_deploy.php --output ./private/scripts/new_relic_deploy.php
pantheon.ymlfile if one doesn't already exist in your root directory.
Paste the following workflow into your
pantheon.ymlfile to hook into the platform after code is synced on Dev/Multidev and deployed to Test/Live to fire off the New Relic® integration script:pantheon.yml
api_version: 1 workflows: # Log to New Relic when deploying to test or live. deploy: after: - type: webphp description: Log to New Relic script: private/scripts/new_relic_deploy.php # Also log sync_code so you can track new code going into dev/multidev. sync_code: after: - type: webphp description: Log to New Relic script: private/scripts/new_relic_deploy.php
api_versionshould be set once in
pantheon.yml. If you have an existing
pantheon.ymlwith this line, do not add it again.
Add, commit, and push changes to the Dev/Multidev environment:
git add private/scripts/new_relic_deploy.php git commit -am "Adding deployment recording to New Relic" git push origin master
In the terminal, you should see that your
pantheon.ymlfile is being applied. Even this initial code push should appear in your Dev environment's New Relic® account, on the Deployments tab:
Confirm that there are no issues, then deploy your new commit to Test and Live. Your deploys will now be recorded in New Relic® Performance Monitoring.
The steps above provide a fast way to integrate New Relic® Performance Monitoring and Pantheon with Quicksilver. The Quicksilver Examples repository provides many more ways to automate development, so please take advantage of them and extend them to fit your workflow.