Juniper Networks ONES 4.1 outlines telemetry control, monitoring, and threshold alerts

ONES Release 4.1 adds Telemetry Preferences for dynamic telemetry control, plus ONES Monitoring to publish host and Docker container health metrics into the existing telemetry pipeline, alongside rule engine support for threshold-based alerts and UI visualization.

Research Overview

The vendor describes ONES 4.1 as an update aimed at improving observability, operational control, and efficiency in modern network environments.

The release is positioned around three additions: dynamic telemetry management via Telemetry Preferences, automated host and container health visibility through ONES Monitoring, and readiness for proactive alerting and visualization through rule engine integration.

Key Findings

Earlier ONES versions collected telemetry using an always-on approach that automatically subscribed to all available telemetry paths from each device, which the post says increased data volume and noise.

Telemetry Preferences in 4.1 is presented as a way to enable or disable telemetry categories, including a default platform category, feature protocol telemetry, and QoS telemetry, based on operational needs.

Technical Breakdown

Telemetry Preferences supports multiple platforms, including SONiC, Cumulus, Cisco NX-OS, Arista, and Compute platforms. The post says operators can control telemetry collection at a category level rather than collecting all available paths.

Platform Default covers items such as interfaces, power supply units, and fan and environmental metrics and is enabled by default, while Feature Protocol telemetry includes ACL, route capacity, BGP, VXLAN, VLAN, and LACP and is enabled only for actively used features. QoS Telemetry includes traffic prioritization, queue behavior, and performance under load and can be enabled or disabled based on the device role and troubleshooting requirements.

Operational Impact

The post describes ONES Monitoring as an automated system health visibility feature that tracks host-level resources such as CPU, memory, and disk, along with Docker container status and utilization.

It says the monitoring metrics are published into the existing telemetry pipeline to support integration with observability workflows, reducing reliance on manual server health checks and container inspection described for earlier deployments.

Readiness for Alerts and Visualization

For alerting, the post states that ONES 4.1 lays groundwork through rule engine integration that supports defining CPU, memory, and disk utilization thresholds.

It also says alerts trigger automatically when thresholds are breached and that the rule engine integration is intended to pair threshold breaches with UI visualization via rule alert payloads.

Blog Signals brief is a fact-based summary of the vendor blog describing ONES Release 4.1 features: Telemetry Preferences for controlled telemetry collection, ONES Monitoring for host and Docker container health metrics in the telemetry pipeline, and rule engine support for threshold alerts and UI visualization.