# US 2026/0039563 A1 · Telemetry data processing in cluster file system with dynamic registration of metrics for short duration

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0039563 A1
- Document ID: US20260039563A1
- Status: Published application
- Kind: A1
- Application number: 18/791,253
- Filed: 2024-07-31
- Published: 2026-02-05
- Earliest claimed: 2024-07-31
- Assignees: Dell Products L.P.
- Applicants: Dell Products L.P.
- Inventors: Bhimsen Bhanjois; Supriya Kannery; Philip Shilane; Rajat Badola
- Web page: https://patentgrep.com/patent/US20260039563A1

## CPC

- H04L 41/147: for predicting network behaviour
- H04L 67/12: specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A telemetry processing system in a cluster network generates telemetry data from a plurality of telemetry producers and formats it into a structured format for storage in a datastore. Producers can define new metrics for use in a running network. Schema for a new metric is validated by a schema validator and stored in a telemetry catalog. For a metric that is to be enabled for only a short duration, the producer registers the metric with a duration and condition for triggering collection of metric datasets. A telemetry collector detects the condition and collects the datasets from the producer and stops collection at the end of the specified duration. Any short-term metric that is no longer needed or requires updating can be unregistered to clean up the telemetry catalog.

## Claims

### Claim 1

A method of processing telemetry data in a cluster network having a plurality of nodes, comprising:
storing the telemetry data as generated by telemetry producers in the network in a datastore as metric datasets having a defined schema;
defining a short-term metric as a metric to be collected for a short duration;
registering the short-term metric with a metric schema, defined duration, and condition for triggering collection of the metric;
initiating, upon detection of the condition, collection of the short-term metric;
stopping collection of the metric at the end of the defined duration; and
unregistering any short-term metric that is no longer needed or requires updating to clean up the telemetry catalog.

### Claim 2 (depends on 1)

The method of claim 1 further comprising mapping a function of the short-term metric to the condition.

### Claim 3 (depends on 1)

The method of claim 1 wherein the telemetry data comprises data generated periodically by each producer upon operation in the cluster network, and consists of performance data, topology information, alerts, security states, and service features.

### Claim 4 (depends on 3)

The method of claim 3 wherein the telemetry data comprises log data, and the short-term metric comprises trace data of the cluster network.

### Claim 5 (depends on 4)

The method of claim 4 wherein the duration is on the order of hours or days.

### Claim 6 (depends on 5)

The method of claim 5 wherein the producer comprises a security node.

### Claim 7 (depends on 1)

The method of claim 1 further comprising storing the short-term metric schema, duration, and condition in a telemetry catalog accessible by a telemetry transmitter, and wherein the short-term metric is collected for transmission by the telemetry transmitter to one or more consumers of the telemetry data, the one or more consumers comprising at least one of:
pod components of the nodes, storage users, graphical user interfaces (GUI), and storage vendors.

### Claim 8 (depends on 7)

The method of claim 7 wherein the producer is provided with a telemetry library for connection through an application programming interface (API) in the telemetry transmitter for registering the schema of the short-term metric.

### Claim 9 (depends on 7)

The method of claim 7 wherein the defining and registering steps are performed while the network is running and executing applications, in order to maintain up-to-date collection of short-term metrics generated by producers in the cluster network.

### Claim 10 (depends on 9)

The method of claim 9 wherein the cluster network includes a telemetry pipeline implementing an Open Telemetry (OTEL) protocol, and wherein the telemetry transmitter includes a collector receiving the telemetry data from producers through a remote procedure call (RPC) process, and further wherein cluster network includes nodes each containing a plurality of pods performing network functions and generating the telemetry data for transmission to the consumers.

### Claim 11

A method of processing telemetry data in a cluster network having a plurality of telemetry producers each periodically generating metric datasets, comprising:
first receiving schema definitions of metric datasets of the telemetry data produced by the telemetry producers;
storing the schema definitions in a telemetry catalog accessed by a telemetry transmitter;
defining a short-term metric as a metric to be collected for a short duration, wherein the short-term metric comprises a metric collected upon occurrence of a condition;
second receiving a schema definition for a short-term metric dataset produced by a producer;
storing the schema definition, duration, and condition for the short-term metric in the telemetry catalog; and
collecting, by the telemetry transmitter and for the duration, the short-term metric dataset, upon detecting the occurrence of the condition.

### Claim 12 (depends on 11)

The method of claim 11 wherein the telemetry data comprises data generated periodically by each producer upon operation in the cluster network, and consists of performance data, topology information, alerts, security states, and service features, and further wherein the one or more consumers comprises at least one of: pod components of the nodes, storage users, graphical user interfaces (GUI), and storage vendors.

### Claim 13 (depends on 12)

The method of claim 12 wherein the cluster network comprises a Santorini network processing containerized data utilizing a Kubernetes-based framework, and further wherein the plurality of nodes each contain a plurality of pods performing network functions and generating the telemetry data for transmission to the subscribing consumers, and further wherein the telemetry data comprises log data, and the short-term metric comprises trace data of the cluster network.

### Claim 14 (depends on 13)

The method of claim 13 wherein the duration is on the order of hours or days, and wherein the producer comprises a security pod.

### Claim 15 (depends on 11)

The method of claim 11 wherein the metric datasets and short-term metric data are collected and registered by the telemetry transmitter while the network is running and executing applications, in order to maintain up-to-date collection of short-term metrics generated by producers in the cluster network.

### Claim 16 (depends on 11)

The method of claim 11 wherein the producer is provided with a telemetry library for connection through an application programming interface (API) in the telemetry transmitter for registering the short-term schema.

### Claim 17 (depends on 16)

The method of claim 16 wherein the telemetry transmitter interfaces with the producer through a telemetry handler to provide notification of the occurrence of the condition to trigger the producer to transmit the short-term metric dataset to a datastore for collection by the telemetry transmitter.

### Claim 18 (depends on 17)

The method of claim 17 further comprising:
processing the short-term telemetry dataset in the telemetry handler the producer; and
inputting the telemetry data to the datastore through a telemetry pipeline, wherein the telemetry pipeline implements an Open Telemetry (OTEL) protocol, and comprises a collector receiving the telemetry data through a remote procedure call (RPC) process.

### Claim 19

A system processing telemetry data in a cluster network having nodes each containing a plurality of pods, the system comprising:
a datastore storing the telemetry data as generated by telemetry producers in the network in a datastore as metric datasets having a defined schema;
a producer pod defining a short-term metric as a metric to be collected for a short duration;
a telemetry transmitter component registering the short-term metric with a metric schema, defined duration, and condition for triggering collection of the metric; and
a telemetry collector component initiating, upon detection of the condition, collection of the short-term metric, and stopping collection of the metric at the end of the defined duration.

### Claim 20 (depends on 19)

The system of claim 19 wherein the cluster network comprises a Santorini network processing containerized data utilizing a Kubernetes-based framework, and further wherein the plurality of nodes each contain a plurality of pods performing network functions and generating the telemetry data for transmission to the subscribing consumers, and yet further wherein the telemetry data comprises data generated periodically by each producer upon operation in the cluster network, and consists of performance data, topology information, alerts, security states, and service features, and the one or more consumers comprises at least one of: pod components of the nodes, storage users, graphical user interfaces (GUI), and storage vendors, and yet further the telemetry data comprises log data, and the short-term metric comprises trace data of the cluster network, and the duration is on the order of hours or days.
