The configuration guide is no longer being updated. Please refer to the CloudVision Help Center going forward.

Features

The list the current supported and unsupported Telemetry platform features are provided in the following topics:

Supported Features

The CVP Telemetry Supported Features table lists the supported features. Review the supported features to ensure you are aware of the features available to you to monitor devices using Telemetry data.

Table 1. CVP Telemetry Supported Features
Supported Feature
Real-time monitoring of devices The Telemetry platform provides interfaces for viewing real-time updates about changes in device state as well as events. You can also view trends in device-state metrics and queries of historical device-state data.
Instant state change updates Changes in the state of a device are instantly streamed to CVP.
Full state change data

All changes in device-state are captured and streamed to CVP for viewing. Types of device-state include:

  • All SysDB state (except state under /Sysdb/cell/*).
  • All SMASH tables.
  • Process and kernel data (for example, CPU and memory usage).
  • System log messages
Analytics engine The Telemetry platform provides a robust analytics engine that aggregates the streamed device-state data across devices, monitors device state, and generates events to indicate issues. It also normalizes data so it is easier for other applications to use.
Telemetry events

Device-state and system environment event types are streamed to CVP:

  • Informational (updates about changes in device state).
  • Warning (for example, unsupported EOS version on a device)
  • Errors (data discards or input errors on interfaces, and more).
  • Critical (system environment issues such as overheating).
High performance database

The Telemetry platform utilizes a high performance Hbase database to store device-state data, including events. Data is stored in compressed format without a loss of resolution.

  • The data storage capacity is approximately:
  • 43200 records worth of raw data per path
  • 5 days of 10 second aggregated data
  • 4 weeks of 60 second aggregated data
  • 3 months worth of 15 minute aggregated data
Disk space protection

To prevent telemetry data from consuming too much disk space in the CVP cluster, the Telemetry platform automatically blocks the ingest port for the entire cluster if disk usage exceeds 85% on any node of the cluster.

Once the ingest port is blocked, it remains blocked until disk usage drops below 80% on all nodes in the cluster.
Data management

To ensure that the most relevant data is given priority, the Telemetry platform provides automated data management, including:

  • Maximum time limit on stored device-state data (1 month).
  • Current and the most recent device-state updates are always stored (given priority over older state updates).

Periodic clean-up jobs are executed weekly (Saturday at 11:00 P.M.). Old device-state data is purged.

Command support

Several commands are provided for:

  • Checking status of the Telemetry components.
  • Enabling and disabling of Telemetry platform components.
  • Starting and stopping Telemetry components.
  • Viewing the debug log for Telemetry components.
  • Troubleshooting the Telemetry components, including checking to see that logs are being created for the component.
  • To display granular information on disk space usage of telemetry data and delete telemetry data selectively.

Unsupported Features

The CVP Telemetry Unsupported Features table lists the unsupported features. Review the limitations to ensure you do not inadvertently attempt to configure or use unsupported Telemetry features.

Table 2. CVP Telemetry Unsupported Features
Unsupported Feature
Streamed device-state data Flexroute is not supported.