Telemetry Collector System Requirements

Telemetry Collector is available for Docker or Kubernetes environments. Note: The Podman container environment is not supported.

Container Runtime

Telemetry Collector requires a container runtime on a Linux host.

Minimize Data Loss with Multi-node Resiliency (Kubernetes only)

To leverage native Kubernetes capabilities for node health monitoring and automatic pod rescheduling in the event of a node failure, follow the instructions below for multiple node resiliency for the Telemetry Collector. The instructions differ slightly based on whether the data source is establishing the connectivity to the Telemetry Collector (e.g. MDT Dial Out), or vice-versa (e.g. gNMI Dial In or SNMP device polling or Kafka)

Note Telemetry Collector is always paired with a Sensor Collector. Sensor Collector configuration requirements for multi-node resiliency are outlined here.

1. Data source establishes connectivity with Telemetry Collector - VIP required

In environments that have a device/router establishing connectivity with the Telemetry Collector (e.g. MDT Dial Out), a customer-provided LoadBalancer Kubernetes service must be configured to assign a Virtual IP (VIP) to the Telemetry Collector. This ensures that a stable, unchanging IP address remains available to the device even if a node failure occurs within the cluster.

Coming Soon: Updated Helm charts and a Telemetry Collector Service will be provided to allow the customer to leverage this in our offering; until then, the customer must set this up themselves.

2. Telemetry Collector establishes connectivity with the data source - no configuration required

In this use case there is no specific configuration required - native Kubernetes behaviour will re-establish the Telemetry Collector on a healthy node, and the Telemetry Collector will re-establish its connectivity to the data source, thus achieving a re-established data flow.

Network Services

The following host services are not strictly required but are recommended for reliable operation:

DNS resolver — Required if endpoints are configured using FQDNs to connect to Sensor Collector, OCSP servers, or monitored network devices. If only IP addresses are used, DNS is not needed. Ensure /etc/resolv.conf on the host points to a functional DNS server. Docker passes this configuration into containers automatically.

NTP client — Telemetry Collector timestamps all collected metrics using the container's system clock, which inherits from the host. Clock accuracy affects the validity of time-series data and correlation with other data sources. Use any standard NTP client on the host (chrony recommended).

HTTP/HTTPS proxy — In environments without direct internet access, pass proxy settings to the container via environment variables: http_proxy, https_proxy, no_proxy. Both lowercase and uppercase variants are supported. See HTTP/HTTPS Proxy for details.

Firewall Rules

If a firewall is active on the host or in the network path, ensure the following traffic is permitted: