Cisco Model-driven Telemetry MonitoringUse This InfluxDB Integration for Free
Cisco Telemetry is a mechanism to stream data from an MDT-capable device to a destination. It uses a push model and provides near real-time access to operational statistics for monitoring data. You can subscribe to the data by using standards-based YANG data models over open protocols.
Why use the Cisco Model-Driven Telemetry Telegraf Plugin?
If you are part of a network operations team, the ability to collect data in near real time is important for network visibility and performance. MDT-capable devices can stream telemetry data using MDT, and the Cisco Model-Driven Telemetry Telegraf Plugin will allow you to consume this data in InfluxDB. Once in InfluxDB, you can visualize the data in InfluxDB, Grafana, or your own custom dashboards. Dashboards of this telemetry data will prove useful with your day-to-day operations, automation and planning of your network. In addition, if you have devices using other protocols like SNMP, you can gain a holistic view of all your network devices.
How to monitor Cisco Model-driven Telemetry using the Telegraf plugin
Cisco Model-Driven Telemetry (MDT) is a Telegraf input plugin that consumes telemetry data from Cisco IOS XR, IOS XE and NX-OS platforms. It supports TCP & GRPC dialout transports. GRPC-based transport can utilize TLS for authentication and encryption. Telemetry data is expected to be GPB-KV (self-describing-gpb) encoded.
The GRPC dialout transport is supported on various IOS XR (64-bit) 6.1.x and later, IOS XE 16.10 and later, as well as NX-OS 7.x and later platforms. The TCP dialout transport is supported on IOS XR (32-bit and 64-bit) 6.1.x and later.
Configuring this plugin is simple, allowing for configuration options like transport, service address and certs.
Key Cisco Model-Driven Telemetry Metrics to use for monitoring
Some of the important Cisco Model-Driven Telemetry metrics that you should proactively monitor include:
- Memory and CPU utilization
- Interface counters and interface summary
- ISIS route counts and ISIS interfaces
- BGP neighbors, path count prefix count
- Bandwidth allocation for each interface