ONES details telemetry preferences and built-in system monitoring
ONES 4.1 adds configurable telemetry controls and built-in host and container monitoring to improve network observability and operational efficiency, giving IT and security leaders clearer telemetry management and integrated health metrics.
Research Overview
Version 4.1 introduces a shift from always-on data collection to selectable telemetry capture and integrates host resource and container status into the telemetry stream. The update lists support for SONiC, Cumulus, Cisco NX-OS, Arista, and compute platforms.
Key Findings
Operators can choose platform default telemetry and enable feature-level or Quality of Service (QoS) metrics only for active use, reducing extraneous data. Host Central Processing Unit (CPU), memory, disk, and Docker container metrics are now published into the existing telemetry pipeline for unified visibility.
Technical Breakdown
Telemetry preferences are grouped to cover platform and hardware state, feature and protocol data, and QoS measurements so teams can tailor collection to operational roles. The monitoring component collects host and container resource metrics and forwards them to the rule engine for use in alerts and dashboards.
Operational impact
Selective telemetry capture aims to lower data volume and reduce collector load while maintaining consistent behavior across supported platforms. Thresholds for CPU, memory, and disk utilization can be defined to trigger automated alerts, enabling earlier identification of resource issues.
Product update
ONES 4.1 provides UI elements for configuring telemetry preferences and surfaces monitoring data for visualization and rule-based alerting. The release positions the platform to feed existing workflows with both device and system health metrics.
ONES 4.1 centralizes telemetry control and system health data to help enterprise teams align observability with operational requirements. The release is relevant to IT and security leaders responsible for telemetry strategy and infrastructure reliability. This “Blog Signals brief” is a fact-based summary of the vendor blog.