Installing and Configuring VMware Tanzu Observability by Wavefront Nozzle

This topic describes how to install and configure VMware Tanzu Observability by Wavefront Nozzle.

Create a Wavefront Account

The VMware Tanzu Observability by Wavefront Nozzle 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
   

   YOUR-SYSTEM-DOMAIN can be found in the Opsman TAS tile on ‘Domains’ page.

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
   

   ADMIN-CLIENT-CREDENTIALS-SECRET can be found in the Opsman TAS tile, on the Credentials tab under ‘UAA’, in “Admin Client Credentials”

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 VMware Tanzu Observability by Wavefront Nozzle 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 VMware Tanzu Observability by Wavefront Nozzle. This adds the tile to your staging area.

4. Click the newly added VMware Tanzu Observability by Wavefront Nozzle tile.

5. Click Wavefront Proxy Config.

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

   1. Wavefront Instance URL: A URL such as https://YOUR_INSTANCE.wavefront.com/api
   2. Wavefront API Token: An 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 the API Access tab for the API 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. You can optionally override the proxy configuration and preprocessor rules under Custom settings.

7. Click Save.

8. Click Wavefront Firehose Nozzle Config.

9. Enter the following information on the Wavefront Firehose Nozzle Config page:

   1. CF API Hostname: The VMware Tanzu API Hostname such as api.YOUR-SYSTEM-DOMAIN.
   2. CF UAA Username/CF UAA Password: The username and password that you created in the Create a UAA Admin User step.
   3. CF API log stream URL: The CF API log stream URL such as https://log-stream.YOUR-SYSTEM-DOMAIN. Required for the v2 Nozzle API.
   4. VMware Tanzu foundation name: A user-friendly foundation name. This is included as a point tag on the metrics sent to Wavefront.
   5. Skip SSL Verification: Select to skip SSL validation. Use this option in non-production environments.
   6. Advanced Nozzle Options:
      1. Select No for the default nozzle settings.
      2. Optionally, selecy Yes and configure the advanced nozzle options such as filters, v1 API mode, number of nozzle instances etc.

10. Click Save.

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

Configure Service Instance for Wavefront Service Broker for VMware Tanzu

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.