Automatically Label Code Changes in New Relic®; Performance Monitoring using Quicksilver Hooks

A guide to integrating Pantheon and New Relic®; Performance Monitoring for deployment labeling.

Contributors: Scott Massey.

Discuss in our Forum Discuss in Slack

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 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 see if a code change positively or negatively impacted performance.

Activate New Relic® Performance Monitoring Pro

Follow the instructions at New Relic APM Pro to activate New Relic® Performance Monitoring for your site.

Configure Quicksilver Hook to Record Deployments

Next, we'll 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 we begin, set the variable $site in your terminal session to match your site name:

export site=yoursitename
  1. If you haven't done so already, clone your Pantheon site repository and navigate to the project's root directory. You can use Terminus to provide the clone command:

    terminus connection:info $ --fields='Git Command' --format=string
    git clone ssh:// sitename

    After you copy and run the output command, change directory to the site code root:

    cd $site
  2. Set the connection mode to Git:

    terminus connection:set $ git
  3. Create a copy of Pantheon's new_relic_deploy.php script in the project's private path:

    mkdir -p private/scripts
    curl --output ./private/scripts/new_relic_deploy.php
  4. Create a pantheon.yml file if one doesn't already exist in your root directory.

  5. Paste the following workflow into your pantheon.yml file 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:

    api_version: 1
      # Log to New Relic when deploying to test or live.
          - 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.
          - type: webphp
            description: Log to New Relic
            script: private/scripts/new_relic_deploy.php


    api_version should be set once in pantheon.yml. If you have an existing pantheon.yml with this line, don't add it again.

  6. Add, commit, and push changes to the Dev 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.yml file is being applied. Even this initial code push should appear in your Dev environment's New Relic account, on the Deployments tab:

    Deployment tab display

  7. Once you've tested and confirmed there are no issues, deploy your new commit to Test and Live. From now on, your deploys will be recorded in New Relic® Performance Monitoring.


This is a fast way to integrate New Relic® Performance Monitoring and Pantheon. The Quicksilver Examples repository provides many more ways to automate development, so please take advantage of them and extend them to fit your workflow.