> [!CAUTION]
> You are currently viewing version 1.2 of the Apigee hybrid documentation. **This version is end of life.** You should upgrade to a newer version. For more information, see [Supported versions](https://docs.cloud.google.com/apigee/docs/hybrid/supported-platforms.md.txt#supported-versions).

<button class="button button-with-icon cloud-select-dropdown__button button-primary" aria-haspopup="true">Version 1.2 (unsupported)</button>

- Supported versions:
- [v1.17 (latest)](https://docs.cloud.google.com/apigee/docs/hybrid/v1.17/other-data-collection.md.txt)
- [v1.16](https://docs.cloud.google.com/apigee/docs/hybrid/v1.16/other-data-collection.md.txt)
- [v1.15](https://docs.cloud.google.com/apigee/docs/hybrid/v1.15/other-data-collection.md.txt)
- [v1.14](https://docs.cloud.google.com/apigee/docs/hybrid/v1.14/other-data-collection.md.txt)
- [List of supported versions](https://docs.cloud.google.com/apigee/docs/hybrid/supported-platforms.md.txt#supported-versions)
- Unsupported versions:
- [v1.13](https://docs.cloud.google.com/apigee/docs/hybrid/v1.13/other-data-collection.md.txt)
- [v1.12](https://docs.cloud.google.com/apigee/docs/hybrid/v1.12/other-data-collection.md.txt)
- [v1.11](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/other-data-collection.md.txt)
- [v1.10](https://docs.cloud.google.com/apigee/docs/hybrid/v1.10/other-data-collection.md.txt)
- [v1.9](https://docs.cloud.google.com/apigee/docs/hybrid/v1.9/other-data-collection.md.txt)
- [v1.8](https://docs.cloud.google.com/apigee/docs/hybrid/v1.8/other-data-collection.md.txt)
- [v1.7](https://docs.cloud.google.com/apigee/docs/hybrid/v1.7/other-data-collection.md.txt)
- [v1.6](https://docs.cloud.google.com/apigee/docs/hybrid/v1.6/other-data-collection.md.txt)
- [v1.5](https://docs.cloud.google.com/apigee/docs/hybrid/v1.5/other-data-collection.md.txt)
- [v1.4](https://docs.cloud.google.com/apigee/docs/hybrid/v1.4/other-data-collection.md.txt)
- [v1.3](https://docs.cloud.google.com/apigee/docs/hybrid/v1.3/other-data-collection.md.txt)
- [v1.2](https://docs.cloud.google.com/apigee/docs/hybrid/v1.2/other-data-collection.md.txt)
- [v1.1](https://docs.cloud.google.com/apigee/docs/hybrid/v1.1/other-data-collection.md.txt)

Apigee hybrid makes debug, analytics, and deployment status data available to you. This data is
collected by a data collection pod which sends it to the management plane so that you can view and
analyze it and set up monitoring and alerts.

## About the data

All Message Processor (MP) services in hybrid stream debug (when initiated), analytics,
and deployment status data via
TCP to a data collection pod in the cluster. The data collection pod stores the streamed data on the
pod's file system via a fluentd service.

The UDCA (Universal Data Collection Agent) periodically extracts the stored data and sends it to
the UAP (Unified Analytics Platform) service in the management plane. The UAP processes the incoming
analytics and deployment status data and makes it available to you via the hybrid UI or the
[Apigee APIs](https://docs.cloud.google.com/apigee/docs/reference/apis/apigee/rest.md.txt).

Apigee hybrid implements the data collection pod as a [ReplicaSet](https://kubernetes.io/docs/concepts/workloads/controllers/replicaset/) with a minimum of two
replicas.

The following image shows the debug, analytics, and deployment status data collection process:

![Architectural diagram
showing the flow of data starting at the Message Processor, being stored by the UDCP, and ultimately
processed by an Apigee API or the Apigee hybrid UI.](https://docs.cloud.google.com/static/apigee/docs/hybrid/v1.2/images/arch-trace-analytics-status-data.png)

Note that the debug, analytics, and deployment status data is not stored in the
same location or accessed in the same way as the logging and metrics data:

- *Logging and metrics data* are stored on your GCP Project and accessed via a tool such as Stackdriver or whatever you choose to use.
- *Debug, analytics and deployment status data* , on the other hand, is stored in the hybrid management plane and you access it via Apigee services such as the hybrid UI or [Apigee APIs](https://docs.cloud.google.com/apigee/docs/reference/apis/apigee/rest.md.txt).

The following table summarizes the data collected by the data collection pod:

| Type of Data | Dataset Name | Description | Update Frequency | APIs |
|---|---|---|---|---|
| Analytics | `api` | API usage data including transactions per second, cache usage, errors, latencies, request/response sizes, and traffic counts. For more information, see [Apigee Analytics overview](https://docs.cloud.google.com/apigee/docs/api-platform/analytics/analytics-services-overview.md.txt). | Up to 30 second delay | [Analytics admin API](https://docs.cloud.google.com/apigee/docs/reference/apis/apigee/rest/v1/organizations.environments.analytics.admin.md.txt) |
| Deployment Status | `event` | The current deployment status of the API proxy. For more information about how you can see this information, see [View deployment status](https://docs.cloud.google.com/apigee/docs/hybrid/v1.2/ui-deploy-overview#view-deployment-status). | Immediately | [Deployments API](https://docs.cloud.google.com/apigee/docs/reference/apis/apigee/rest/v1/organizations.deployments.md.txt) |
| Debug | `debug` | Debug session data for API proxies. This data includes the request/response parameters along with transformations applied to them at policy execution time. Because of its size, debug data---unlike analytics and deployment status data---is not collected all the time. Instead, debug data is collected when you initiate a debug session. For more information, see [Debug overview](https://docs.cloud.google.com/apigee/docs/hybrid/v1.2/trace). | Immediately | [Debug session API](https://docs.cloud.google.com/apigee/docs/reference/apis/apigee/rest/v1/organizations.environments.apis.revisions.debugsessions.md.txt) [Debug session data API](https://docs.cloud.google.com/apigee/docs/reference/apis/apigee/rest/v1/organizations.environments.apis.revisions.debugsessions.data.md.txt) |

> [!IMPORTANT]
> **TIP:** The *dataset name* is the name by which this type of data is referred to in the UDCA configuration properties. For example, analytics data is configured with the dataset name `api`. As a result, the configuration property that sets the location of the analytics data files is called `apiDataSubDir`.
>
> You can access this data through the Apigee hybrid UI or [Apigee APIs](https://docs.cloud.google.com/apigee/docs/reference/apis/apigee/rest.md.txt) on the management
> plane.

## View the data in the hybrid UI

This section describes how to view the debug, analytics, and deployment status data in the Apigee
hybrid UI.

### Debug

Debug data for hybrid services is accessible in the same way as Edge debug data, with some
differences such as increased filter support. For more
information, see [Debug overview](https://docs.cloud.google.com/apigee/docs/hybrid/v1.2/trace).

### Analytics

Analytics data for hybrid services is accessible in the same way
as Edge analytics data. For more information, see
[Using the analytics dashboards](https://docs.cloud.google.com/apigee/docs/api-platform/analytics/using-analytics-dashboards.md.txt) in
the Edge documentation.

### Proxy deployment status

For information on viewing deployment status, see
[View deployment status](https://docs.cloud.google.com/apigee/docs/hybrid/v1.2/ui-deploy-overview#view-deployment-status).

## Configure the data collection

To set how and where debug, analytics, and deployment status data is
collected on the data collection pod, you configure the UDCA
service via its configuration properties. The UDCA properties
include properties that are general to the UDCA as well as
properties that are specific to each dataset.

**To configure the UDCA:**

1. Open the `overrides.yaml` file for editing on your Kubernetes administration machine, as described in [Manage runtime plane components](https://docs.cloud.google.com/apigee/docs/hybrid/v1.3/customize-services.md.txt).
2. Set the values of the UDCA configuration settings. For the UDCA, you can set custom values for properties such as:
   - Polling interval
   - Number of replicas (min and max)
   - Target CPU percentage (that triggers additional replicas)

   For a complete list of UDCA properties that you can customize,
   see [`udca`](https://docs.cloud.google.com/apigee/docs/hybrid/v1.2/config-prop-ref.md.txt#udca).
3. Save your changes to the overrides.yaml file.
4. Apply your changes to your cluster by executing the `apigeectl apply` command, as the following example shows:

   ```
   apigeectl apply -f my-overrides.yaml -c udca
   ```

   > [!IMPORTANT]
   > **TIP** : To see the default configuration properties, the UDCA service (under `udca:`) in the [Configuration property reference](https://docs.cloud.google.com/apigee/docs/hybrid/v1.3/config-prop-ref.md.txt).

   For more information about the `apply` command, see
   [Apply hybrid to your cluster](https://docs.cloud.google.com/apigee/docs/hybrid/v1.2/cli-reference.md.txt#apply).