Juniper Networks, Inc.

Gauresh Dilip Vanjare

Harshit Naresh Chitalia

Tarun Banka

Rajenkumar Patel

Yixiao Wei

Aditi Ghotikar

Mithun Chakaravarrti Dharmaraj

Shruti Jadon

Venny Kranthi Teja Kommarthi

Keval Nimeshkumar Shah

Mithun Chakarvarrti Dharmaraj

A telemetry service can receive telemetry collection requirements that are expressed as an 'intent' that defines how telemetry is to be collected. A telemetry intent compiler can receive the telemetry intent and translate the high level intent into abstract telemetry configuration parameters that provide a generic description of desired telemetry data. The telemetry service can determine, from the telemetry intent, a set of devices from which to collect telemetry data. For each device, the telemetry service can determine capabilities of the device with respect to telemetry data collection. The capabilities may include a telemetry protocol supported by the device. The telemetry service can create a protocol specific device configuration based on the abstract telemetry configuration parameters and the telemetry protocol supported by the device. Devices in a network system that support a particular telemetry protocol can be allocated to instances of a telemetry collector that supports the telemetry protocol.

Intent-based telemetry collection service with supported telemetry protocol in a virtualized computing infrastructure

Techniques for resource monitoring and managed message reordering in a data center are described. In one example, a computing system comprises an ingress engine to receive a message from a network device in a data center comprising a plurality of network devices and the computing system; and in response to receiving the message from a network device in the data center, communicate the message to an appropriate collector application corresponding to the message's protocol type in compliance with at least one requirement for data stored in a message flow communicated from one or more network devices to the computing system.

Data center resource monitoring with managed message load balancing with reordering consideration

An alarm service can receive an alarm rule as an 'intent' that defines a rule in a high level 'natural language.' An alarm rule compiler can receive the intent and translate the high level intent into one or more lower level rules that can be programmatically processed by multiple alarm rule execution engines. Devices in a network system can be associated with alarm rule execution engines in a distributed manner. For example, devices in a network can be associated with different instances of an alarm rule execution engine, thus distributing the resource usage for obtaining telemetry data and processing alarms with respect to the devices in a network across multiple alarm rule execution engines.

Intent-based distributed alarm service

Growing community of inventors

Santa Clara, CA, United States of America

Gauresh Dilip Vanjare