Telemetry Collector System Requirements

A single Telemetry Collector instance can ingest data from one or more devices.

A single data ingestion pipeline (which is comprised of a Telemetry Collector paired with a Sensor Collector) can handle 19,500 metric records being streamed to it from device(s) every 1 second (or at a less frequent cadence, depending on the user's requirements).

If more than 19,500 records at 1-second streaming are required, multiple data ingestion pipelines (Telemetry Collectors and Sensor Collectors) can be deployed to handle the requirements.

Note: Any additional software running on the virtual machine(s) that house the Telemetry Collector and Sensor Collector will require additional processor and memory resources; the compute requirement specifications above are only for the data ingestion pipeline components.

Solution Engineers can decide whether to deploy the Sensor Collector and Telemetry Collector on a single virtual machine or, as an alternative, they can each be deployed on separate machines that have one-to-one pairing.

The tables below list the default, out-of-the-box telemetry objects for IOS-XE and IOS-XR, including the number of metrics for each object.

IOS XR Default Objects:

IOS XE Default Objects:

Container Runtime

Telemetry Collector requires a container runtime on a Linux host.

Note: The Podman container environment is not supported.

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: