--- title: "Adding a Telemetry Aggregator" slug: "adding-a-telemetry-aggregator-v7-0" description: "Configure the Telemetry Aggregator to collect performance signals from appliances, ensuring secure communication and integration with monitoring tools." tags: ["Observability", "Telemetry Aggregator", "Appliance Configuration", "Appliance Functions"] updated: 2026-11-09T14:47:01Z published: 2026-11-09T14:47:01Z canonical: "support.appgate.com/adding-a-telemetry-aggregator-v7-0" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.appgate.com/llms.txt > Use this file to discover all available pages before exploring further. # Adding a Telemetry Aggregator The Telemetry Aggregator receives performance signals—such as logs, traces, and system metrics—from multiple appliances in your Collective. Once the data is collected, the Telemetry Aggregator sends it to your preferred monitoring tool or security platform (SIEM), such as Grafana LGTM or OpenObserve. This section describes how to configure a Telemetry Aggregator on an AppGate system. For more information about telemetry in AppGate ZTNA, or how to configure a SIEM or observability platform to receive telemetry data from AppGate ZTNA, see [Using AppGate ZTNA telemetry](/v1/docs/appgate-telemetry-v7-0). > [!NOTE] > NOTE > > The Telemetry Aggregator is part of the [Observability](/v1/docs/observability-v7-0) license (formerly Digital Experience Monitoring), and will appear once that license is uploaded. No action is required for users that already have a Digital Experience Monitoring license. --- ## Before adding a Telemetry Aggregator Before configuring a Telemetry Aggregator, ensure the appliance-to-appliance communication is set up correctly: - AppGate uses single packet authorization (SPA) for appliance-to-appliance communication. Firewalls configured to allow all TLS traffic can interfere with SPA. It is therefore recommended to allow TCP port 443 between appliances. - The Telemetry Aggregator accepts incoming traffic from peer appliances and must be reachable from all appliances. Other members of the Collective establish connections to send audit logs, traces, and metrics (see [Audit logs](/v1/docs/audit-logs-v7-0) for details). - A static IP address or resolvable hostname must be configured in [System Settings](/v1/docs/adding-a-new-appliance-v7-0#system-settings). --- ## Configuring a Telemetry Aggregator To configure a Telemetry Aggregator: 1. In the **Add/Edit Appliance** page, select the ***Telemetry Aggregator*** checkbox in the **Functions** tab. 2. Complete the following configuration fields: ### Site Settings - ***Appliance Site***. Select the Site from the dropdown list. ### System TLS Connection (using SPA) These settings are used for peer‑to‑peer traffic: - ***TLS Port***. The inbound TLS connection port to the appliance. - ***Allowed Sources***. Select **+Add** to add one or more allowed sources by adding the *Address*, *Netmask Length*, and the *Network Interface*. The requesting IP address must match at least one allowed source. - ***SPA Mode***. Allows the SPA mode to be changed for a specific appliance. Select one of the following: - *No override* - *Check TCP SPA key before allowing connections* - *Check UDP (and TCP) SPA key before allowing connections* - ***Enable proxy protocol****.* When enabled, the appliance accepts only packets that include a proxy protocol header. AppGate ZTNA supports proxy protocol versions 1 and 2. > [!NOTE] > NOTE > > When traffic originates from a known source, add that source to *Allowed Sources*. Failure to do so introduces a security risk. ### Telemetry Aggregator Settings Configure the following fields: - ***Datadog Exporters.*** Select **+Add** to configure a Datadog exporter: - *Name.* Enter a name for your Datadog exporter. - *Datadog Site.* Enter the URL of your Datadog site. - *Datadog API Key*. Enter the API key for your Datadog site. - ***OpenTelemetry Protocol Exporters.*** Select **+Add** to add the third-party monitoring platform or SIEM: - *Name*. Enter a name for the exporter. - *Endpoint*. Enter the URL. - *Protocol*. Use the drop-down to select a protocol. The options are **HTTP** and **gRPC**. - *Headers*. Select **+Add** to enter credentials as custom headers—such as an authorization header. Enter them as key-value pairs to include with each export request. - *Enable compression*. Select the checkbox to compress the data. - *Encoding*. Use the drop-down to select an encoding format that your destination accepts. The options are **Protobuf** and **JSON**. After completing the Telemetry Aggregator configuration, continue on to the [**Miscellaneous**](/v1/docs/adding-a-new-appliance-v7-0#miscellaneous) tab.