<commit_before>---
title: Monitor Tanzu Application Service with Tanzu Observability by Wavefront
keywords:
tags: [integrations]
sidebar: doc_sidebar
permalink: integrations_tas_howto.html
summary: Set up the Tanzu Observability tile and monitor your environment.
---

[VMware Tanzu Application Service](), previously known as Pivotal Cloud Foundry, is a popular platform for building cloud-native applications.

This doc page explains:
* How to install and configure the Tanzu Observability by Wavefront nozzle from Tanzu Ops Manager.
* How to access the Tanzu Application Service integration, and what you can do there.

{% include important.html content="This document is for the Tanzu Application Service nozzle version 4.0 and later. Earlier versions are [documented here](https://docs.pivotal.io/wavefront-nozzle/3-x/). " %}

## Overview

Tanzu Observability by Wavefront (Wavefront) is a cloud-hosted service for full-featured observability. When you Tanzu Application Service to send data to the Wavefront proxy, you can take advantage of preconfigured dashboards, customize predefined alerts, and more.

### Data Flow

Here's an overview of the flow of data from the Tanzu Application Service Firehose through the nozzle to the Wavefront service. The nozzle consists of these main components:
- **Healthwatch Exporters**: Exporters are deployed as VMs.
- **Telegraf**: An open source, lightweight server process for collecting, processing, and aggregating metrics.
- [**Wavefront Proxy**](proxies.html): Ingests metrics and forwards them to the
Wavefront service in a secure, fast, and reliable manner

Here's the data pipeline:
1. The Healthwatch Exporter VMs stream metrics from the TAS Firehose. The tile creates a VM for each Healthwatch exporter a VM for Telegraf and a VM for the Wavefront Proxy.
2. Telegraf scrapes the VMs at a predefined interval, and converts them to [Wavefront data format](wavefront_data_format.html).RK>>TRUE?? It's not proxy preprocessor rule(s)
3. The metrics are then sent to the Wavefront Proxy.  RK>>Telegraf sends them?
4. The proxy send the metrics to the Wavefront service.

![TAS Firehose to Exporters like pas-sli-exporter, to Telegraf agent, to Wavefront proxy, to Wavefront service](images/tas-to.png)<commit_msg>New staging branch for sandbox-a<commit_after>---
title: Monitor Tanzu Application Service with Tanzu Observability by Wavefront
keywords:
tags: [integrations]
sidebar: doc_sidebar
permalink: integrations_tas_howto.html
summary: Set up the Tanzu Observability tile and monitor your environment.
---

[VMware Tanzu Application Service](), previously known as Pivotal Cloud Foundry, is a popular platform for building cloud-native applications. 

This doc page explains:
* How to install and configure the Tanzu Observability by Wavefront nozzle from Tanzu Ops Manager.
* How to access the Tanzu Application Service integration, and what you can do there.

{% include important.html content="This document is for the Tanzu Application Service nozzle version 4.0 and later. Earlier versions are [documented here](https://docs.pivotal.io/wavefront-nozzle/3-x/). " %}

## Overview

Tanzu Observability by Wavefront (Wavefront) is a cloud-hosted service for full-featured observability. When you Tanzu Application Service to send data to the Wavefront proxy, you can take advantage of preconfigured dashboards, customize predefined alerts, and more.

### Data Flow

Here's an overview of the flow of data from the Tanzu Application Service Firehose through the nozzle to the Wavefront service. The nozzle consists of these main components:
- **Healthwatch Exporters**: Exporters are deployed as VMs.
- **Telegraf**: An open source, lightweight server process for collecting, processing, and aggregating metrics.
- [**Wavefront Proxy**](proxies.html): Ingests metrics and forwards them to the
Wavefront service in a secure, fast, and reliable manner

Here's the data pipeline:
1. The Healthwatch Exporter VMs stream metrics from the TAS Firehose. The tile creates a VM for each Healthwatch exporter a VM for Telegraf and a VM for the Wavefront Proxy.
2. Telegraf scrapes the VMs at a predefined interval, and converts them to [Wavefront data format](wavefront_data_format.html).RK>>TRUE?? It's not proxy preprocessor rule(s)
3. The metrics are then sent to the Wavefront Proxy.  RK>>Telegraf sends them?
4. The proxy send the metrics to the Wavefront service.

![TAS Firehose to Exporters like pas-sli-exporter, to Telegraf agent, to Wavefront proxy, to Wavefront service](images/tas-to.png)
{'fraction_non_alphanumeric': 0.06398416886543536, 'fraction_numerical': 0.0030782761653474055, 'mean_word_length': 5.089692101740295, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 11, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4651177', 'n_tokens_mistral': 1288, 'n_tokens_neox': 1172, 'n_words': 601}