Datadog Cluster Monitoring for VMware Tanzu

This page is not yet available in Spanish. We are working on its translation.
If you have any questions or feedback about our current translation project, feel free to reach out to us!

Overview

Datadog Cluster Monitoring for VMware Tanzu combines the Datadog Firehose Nozzle with the Datadog Agent, and enables VMware Tanzu users and administrators to monitor the health and performance of their VMware Tanzu clusters. It consists of the following three components:

  • The Datadog Firehose Nozzle
  • The Datadog Agent
  • The Datadog Cluster Agent

The Datadog Firehose Nozzle is a Cloud Foundry component which forwards metrics from the Loggregator Firehose to the Datadog monitoring platform. Any Cloud Foundry deployment can send metrics and events to Datadog. The data helps you track the health and availability of all nodes in your deployment, monitor the jobs they run, collect metrics from the Loggregator Firehose, and more.

Prerequisites

Datadog Cluster Monitoring for VMware Tanzu has the following requirements:

Key features

Datadog Cluster Monitoring for VMware Tanzu includes the following key features:

  • Visualization of all cluster-level operational metrics and KPIs.
  • Alerting on VMware Tanzu cluster and component health.
  • Monitoring of jobs.
  • Tracking and reporting of BOSH events.
  • Autodiscovery of integrations.

Installation

  1. Download the Datadog Cluster Monitoring for VMware Tanzu product file from Pivotal Network.

  2. Go to the Tanzu Ops Manager installation dashboard and click Import a Product to upload the product file.

  3. Click Import a Product to upload the product file.

  4. Select the product file downloaded in step 1. This adds the tile to your staging area.

  5. Click the newly added Datadog Cluster Monitoring for VMware Tanzu tile.

  6. Enter your Datadog API key in the Datadog Config section. Leave the Datadog API URL unchanged, unless directed otherwise by Datadog Support.

  7. Create a UAA client account for Datadog using the UAA CLI. The Firehose Nozzle requires access to the Loggregator Firehose.

    $ uaac client add datadog-firehose-nozzle \
         --name datadog-firehose-nozzle \
         --scope doppler.firehose,cloud_controller.admin_read_only,oauth.login \
         --authorities doppler.firehose,cloud_controller.admin_read_only,openid,oauth.approvals \
         --authorized_grant_types client_credentials,refresh_token \
         --access_token_validity 1209600 \
         -s $CLIENT_SECRET
    
  8. In the Cloud Foundry Settings section, specify a UAA Client and UAA Secret from the previous step.

  9. If Ops Manager requires you to upload a stemcell, download a stemcell from the 621 line of releases. Upload it to Ops Manager with the Import Stemcell button.

  10. The Datadog Firehose Nozzle Config section contains optional configurations for the Nozzle, and the Datadog Agent Config section contains optional configurations for the Agent. You do not need to configure anything in either section.

    Note: If you are using a single Datadog account to monitor multiple foundations, you must check the Use UUID Hostname checkbox.

  11. The Datadog Cluster Agent Settings section contains configurations for the Datadog Cluster Agent that provides autodiscovery of integrations and application container features. Enter an Authentication token in the Datadog Cluster Agent Settings, a string of 32 or more characters. This token is shared by both the Cluster Agent and the Datadog Agents to secure communication.

  12. Return to the Tanzu Ops Manager Installation Dashboard and click Apply Changes to install Datadog Cluster Monitoring for the VMware Tanzu tile.

View metrics and dashboards

  1. Review the Cloud Foundry Overview Dashboard.
The Cloud Foundry Overview dashboard
  1. Explore individual metrics on the Metrics explorer page, search for metrics beginning with cloudfoundry.nozzle:
Cloud foundry metrics that start with cloudfoundry.nozzle
  1. Create alerts for your Cloud Foundry metrics.
  2. See the Datadog Cloud Foundry Integration for troubleshooting steps.

Further reading

PREVIEWING: brett0000FF/node-compatibility