Installing and Configuring Wavefront by VMware Nozzle for PCF

This topic describes how to install and configure Wavefront by VMware Nozzle for PCF.

Create a Wavefront Account

The Wavefront by VMware Nozzle for PCF requires that you have a Wavefront account with an API access token. If you need an account, contact Wavefront Sales.

Create a UAA User Account

Create a UAA user with access to the Firehose and Cloud Controller:

  1. Target your system with the UAA CLI (UAAC): $ uaac target https://uaa.YOUR-SYSTEM-DOMAIN
  2. Run the following command to authenticate and obtain an access token for the admin client from the UAA server. $ uaac token client get admin -s ADMIN-CLIENT-CREDENTIALS-SECRET
  3. Create a Wavefront Nozzle user with the password of your choosing. $ uaac -t user add wavefront-nozzle --password PASSWORD --emails na
  4. Add the user to the Cloud Controller Admin Read-Only group. uaac -t member add cloud_controller.admin_read_only wavefront-nozzle
  5. Add the user to the Doppler Firehose group. $ uaac -t member add doppler.firehose wavefront-nozzle

For information about creating a UAA user, see Creating and Managing Users with the UAA CLI.

Install and Configure Wavefront by VMware Nozzle for PCF in Ops Manager

  1. Download the product file from Pivotal Network.

  2. Navigate to the Ops Manager Installation Dashboard and click Import a Product to upload the product file.

  3. Under the Import a Product button, click + next to the version number of Wavefront by VMware Nozzle for PCF. This adds the tile to your staging area.

  4. Click the newly added Wavefront by VMware Nozzle for PCF tile.

  5. Click Wavefront Proxy Config. Configure Proxy

  6. Enter the following in the Wavefront Proxy Config pane:

    1. Wavefront Instance URL: A URL such as
    2. Wavefront API Token: API access token from the profile page on your Wavefront instance.
      1. Click the gear icon on the top right in Wavefront
      2. Click your username
      3. Click on the API Access tab for the API Token: API Access Token
    3. User friendly hostname: A unique hostname for the proxy such as DOMAIN-pcf-proxy
    4. CF Quota Name: A CF org quota with at least 20 GB memory and a route and port available.
    5. Custom Proxy configuration: Choose Default for the default proxy settings. Optionally, you can override the proxy configuration and preprocessor rules under Custom settings.
  7. Click Save.

  8. Click Wavefront Firehose Nozzle Config. Configure Nozzle

  9. Enter the following in the Wavefront Firehose Nozzle Config section:

    1. CF API Hostname: The PCF API Hostname such as api.YOUR-SYSTEM-DOMAIN
    2. CF UAA Username/CF UAA Password: Enter the username and password you created in the Create a UAA Admin User step, above.
    3. PCF foundation name: A user friendly PCF foundation name. This is included as a point tag on the metrics sent to Wavefront.
    4. Skip SSL Verification: Check to skip SSL validation. This is useful in non-production environments.
    5. Metrics White List: Optional comma separated list of glob patterns such as pcf.container.*. Only metrics with names matching the whitelist are reported.
    6. Metrics Black List: Optional comma separated list of glob patterns. Metrics with names matching the blacklist are dropped.
  10. Click Save.

  11. Return to the Ops Manager Installation Dashboard and click Apply changes to install Wavefront by VMware Nozzle for PCF tile.

Configure Service Instance for Wavefront Service Broker for PCF

Follow the steps below to enable developers to send app metrics to the Wavefront Proxy:

  1. To provision a wavefront-proxy service instance: cf create-service wavefront-proxy standard SERVICE_INSTANCE_NAME
  2. To bind apps to the service instance: cf bind-service APP_NAME SERVICE_INSTANCE_NAME
  3. For information about how apps can send metrics to the Wavefront Proxy, see the cloud-foundry-sampleapp.
Create a pull request or raise an issue on the source for this page in GitHub