New Relic Service Broker for PCF

This is documentation for the New Relic Service Broker for Pivotal Cloud Foundry (PCF) tile.

New Relic APM supports real-time instrumentation and monitoring of application performance via its embedded agent that runs with apps.

New Relic agent code publishes performance monitoring metrics and other details back to New Relic APM Dashboard.

The language agents also send all of the application and browser events to New Relic Analytics tool, Insights, for visualization and dashboarding.

New Relic Service Broker

A service broker allows Cloud Foundry apps to bind to services and consume the services easily from Pivotal Apps Manager or from the command line.

New Relic Service Broker for PCF enables you to use one or more New Relic accounts and is deployed as a Java app on PCF.

The broker exposes the New Relic service on the Marketplace and allows users to directly create a service instance and bind it to their apps either from Apps Manager or from the command line.

The New Relic Service Broker for PCF tile installs the New Relic Service Broker as an app, registers it as a service broker on PCF, and exposes its service plans on the Marketplace. Each service plan is associated with an existing New Relic account, which is configured during the tile setup.

Selecting a plan binds your app with the New Relic agent, and the agent starts reporting to the New Relic account which is associated with the selected plan. This makes the installation and subsequent use of New Relic on your PCF apps easier and more straightforward.

WARNING: The current tile removes the all_open security group from the tile default security settings. If you are using a previous versions of the tile, make your PCF environment more secure by removing the all_open security group from the Application Security Group (ASG) settings. The new version of the tile does not open the security, nor does it close the security if it was already open.

Trial License

You can obtain a 60-day free trial license.

Product Snapshot

Note: As of PCF v2.0, Elastic Runtime is renamed Pivotal Application Service (PAS).

The following table provides version and version-support information about New Relic Service Broker for PCF.

Element Details
Version v1.12.18
Release date August 10, 2018
Software component version New Relic Service Broker v1.12.18
Compatible Ops Manager version(s) v1.12.x, v2.0.x, v2.1.x, v2.2.x, and v2.3.x
Compatible Pivotal Application Service version(s) v1.12.x, v2.0.x, v2.1.x, v2.2.x, and v2.3.x
IaaS support AWS, GCP, Azure, and vSphere

Upgrading to the Latest Version

  • New Relic Service Broker v1.12.18 allows users to change New Relic license key in existing service plans. In v1.12.12 and earlier, the plan unique GUIDs were calculated differently. In order for the plan services to work properly and not break the compatibility, the GUIDs must be the same as before. The "migration script" preserves the plan GUIDs for existing plans in the plan collection for v1.12.12 and earlier. You can see 2 new properties labeled “pre-1.12.12 plan?” and “Plan Guid Override (broker 1.12.12 or older)” in the plan collection for each plan in the tile configuration. Do not change either of these properties, as they are set internally where required. For plans that were created with v1.12.12 or later, leave “pre-1.12.12 plan” unchecked, and “Plan Guid Override” blank.

    Note: The only case where you must override the “Plan Guid Override” property is when you have changed the original license key that was associated with the plan created by New Relice Service Broker v1.12.12 or earlier. You can obtain the original plan GUID from Cloud Controller by running the following command and entering the original GUID in the “Plan Guid Override” property:

    cf curl $(cf curl /v2/services?q=label:newrelic | grep "service_plans_url" | awk '{print $2}' | sed 's/[",]//g') | egrep "\"name\":|\"unique_id\":" | sed 's/[\",]//g' | tr -s " " | awk ' {name=$0; getline; printf("\t%-40s %-40s\n",name,$0)}'

  • The tile is supported on Ops Manager v1.9.x, v1.10.x, v1.11.x, v1.12.x, v2.0.x, v2.1.x, v2.2.x, and 2.3.x.

  • You can install the tile on any of these versions, and upgrade from v1.9.x to any Ops Manager version up to and including v2.3.x.

  • No upgrade paths are required for older verisons of the tile, since versions older than v1.9.0 are not supported.

  • v1.12.6 and later of the tile support migration from older versions of the tile, and preserve existing services and service plans.

  • If you are using tiles older than v1.11.4, you must first upgrade to v1.11.4, then to v1.12.9, then to the latest version of the tile.

Installing Through Ops Manager

To download the New Relic Service Broker for PCF tile and install it on PCF Ops Manager, do the following:

  1. Download the product file from Pivotal Network.

  2. Import the product file to your Ops Manager installation.

  3. Click the + sign or Add next to the uploaded product description in the Ops Manager left navigation view to add this product to your staging area.

  4. Click the newly added tile and review any configurable options.

  5. Click Apply Changes.

Configuring the Tile

  1. Log in to Ops Manager.

  2. Click Import a Product and import the New Relic Service Broker for PCF tile.

    Import product

  3. Click Add on the New Relic Service Broker for PCF tile.


  4. Select the New Relic tile.


  5. Configure the New Relic Service Broker.

    • Click Add on the far right of the Service Plan screen to create a new service plan.


  6. Create a service plan with your New Relic license key.

    • Log in to your New Relic account and navigate to the Account Settings page from the drop-down menu in the upper right corner of the page. Save the plan(s).

    Account info


  7. As of v1.12.3 of the tile, a configuration tab for Service Access has been added, which allows you to decide whether or not the tile should be available globally to all users in all orgs. In v1.12.3, this value is set to false by default, and if you want the tile to be available in the marketplace for all orgs, you must select this checkbox. In v1.12.3 and later, the flag is selected by default, so the tile is available in all orgs.

    Service access

  8. Apply your changes.

  9. On completion of the installation, check the Services Marketplace in Apps Manager.


  10. View New Relic Service Plans.


  11. Bind the New Relic Service to an app.


  12. In a terminal window, run cf restage to make the changes.

      $ cf restage APPNAME
  13. Log in to New Relic to view monitoring data.

    Figure 13.1: New Relic App Monitoring Dashboard

    Figure 13.2: New Relic Transactions View

    Figure 13.3: Transaction Traces View

    Figure 13.4: New Relic Database View

    Figure 13.5: New Relic Web Transactions View

    Figure 13.6: New Relic Top Web Transactions View

    Figure 13.7: New Relic JVMs View

Configuration with HTTP Proxy

If the PCF environment needs to use an HTTP or HTTPS proxy for external outbound communication, the service broker itself does not need to know anything about the HTTP proxy, as it relays the license keys to the consumer apps. The consumer app should specify the http\_proxy or https\_proxy as an environment variable for the agent to communicate externally with non-Java apps, and use JAVA_OPTS for Java apps. In addition, the New Relic Agent should also be configured with its own set of parameters (-Dnewrelic.config.\*) to communicate with its controller through the proxy for Java language apps.

To specify using http_proxy for the New Relic non-Java app agent to talk to its controller using the proxy, run the following commands:

  $ cf set-env APPNAME http_proxy ‘'

  $ cf set-env APPNAME https_proxy ‘'

To specify using JAVA_OPTS for the New Relic Java agent to talk to its controller using the proxy, run the following command:

  $ cf set-env APPNAME JAVA_OPTS " -Dtest.value=barbar
  -Dnewrelic.config.proxy_port=8080 “

If a Java app also needs to talk through a proxy, add the Java proxy settings in addition to the New Relic agent proxy settings with the following command:

  $ cf set-env APPNAME JAVA_OPTS " -Dtest.value=barbar
  -Dnewrelic.config.proxy_port=8080 -Dhttps.proxyPort=8080  “

For a non-Java app that needs to talk outbound using a proxy, run the following commands:

  $ cf set-env APPNAME http_proxy http://user@password:myproxy....:8080/
  $ cf set-env APPNAME https_proxy https://user@password:myproxy....:8080/

Whenever making changes to Cloud Foundry environment variables, you must restage your app(s) to make the changes effective.

  $ cf restage APPNAME

These environment variables can either be set individually per app, or with environment variable groups to be set for all apps as part of staging, running environments, etcetera using the Cloud Foundry Command Line Interface (cf CLI) tool.

Environment Variable Groups

  • running-environment-variable-group/revg: Retrieve the contents of the running environment variable group
  • staging-environment-variable-group/sevg: Retrieve the contents of the staging environment variable group
  • set-staging-environment-variable-group/ssevg: Pass parameters as JSON to create a staging environment variable group
  • set-running-environment-variable-group/srevg: Pass parameters as JSON to create a running environment variable group

Use the JAVA\_OPTS environment variable to specify New Relic Agent-specific environment variables in the staging environment group so the Java buildpack can use that and push it in the correct place. Specifying JAVA\_OPTS in the Runtime environment variable group will not yield anything, as the buildpack will not know about it.

For example:

  $ cf ssevg '{ "JAVA_OPTS" : " -Dtest.value=barbar
  -Dnewrelic.config.log_level=finer ", "test_env_profile" : "Staging" }'

For more information, see Configuration settings precedence.

Packaging Dependencies for Offline Buildpacks

If you are running PCF in an offline manner, you should recreate and package the dependencies, including the New Relic agent binaries, using offline buildpacks in your PCF environment.

For more information, see Packaging Dependencies for Offline Buildpacks.


  • Currently supported buildpacks bundling New Relic Agent are the Java, node.js, PHP, and .NET Core buildpacks.
    • Java Buildpack v2.7+ and v3.x
    • Node.js Buildpack v1.5.19+
    • PHP Buildpack v4.0+
    • .NET Core requires that you push your app using cf v3-push and specify New Relic’s supply buildpack with -b option in the command line as the first buildpack in sequence.


Please provide any bugs, feature requests, or questions to the PCF feedback list.

Create a pull request or raise an issue on the source for this page in GitHub