IP Library Granted Patent US 12,373,322
Granted Patent B2
US 12,373,322 · App. 18/596,591 · Granted Jul 29, 2025

Machine learning for metric collection

Inventors: Raja Kommula (Cupertino, CA); Ganesh Byagoti Matad Sunkada (Bengaluru, IN); Thayumanavan Sridhar (Sunnyvale, CA); Thiraviya Eswaran (Karur, IN); Raj Yavatkar (Los Gatos, CA)
Assignee: Juniper Networks, Inc.
G06F11/3409G06F11/327H04L41/0604H04L41/0609H04L41/0681H04L41/16H04L43/024H04L43/04H04L43/08
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,373,322
App. No.
18/596,591
Granted
Jul 29, 2025
Kind
B2
Abstract

A performance monitoring system includes a metric collector configured to receive, via metric exporters, telemetry data comprising metrics related to a network of computing devices. A metric time series database stores related metrics. An alert rule evaluator service is configured to evaluate rules using stored metrics. The performance monitoring system may include a machine learning module and is configured to determine optimized metric collection sampling intervals and rule evaluation intervals, and to automatically determine recommended alert rules.

Claims (49)

1. A method comprising:

collecting, by a performance monitoring system, telemetry data comprising metrics related to a network of computing devices, wherein, for each metric, metric values associated with a corresponding metric name of the metric are collected at each of a plurality of times according to a first collection sampling interval;

storing, by the performance monitoring system, a query history comprising queries related to the metrics;

generating, by the performance monitoring system, a metric relevance attribute based on an access ratio determined from a portion of the query history corresponding to a first metric of the metrics;

determining, by the performance monitoring system, a predicted metric weight for the first metric based on the metric relevance attribute; and

collecting, by the performance monitoring system, additional telemetry data according to a second collection sampling interval for at least one of the metrics, wherein the second collection sampling interval is based on the predicted metric weight for the first metric.

2. The method of claim 1 ,

wherein the second collection sampling interval is different than the first collection sampling interval, and

wherein collecting the additional telemetry data comprises collecting corresponding metric values for the first metric according to the second collection sampling interval.

3. The method of claim 1 , further comprising:

determining, by the performance monitoring system, whether the first metric is a critical metric; and

based on determining the first metric is a critical metric, using, by the performance monitoring system, a predetermined minimum sampling interval for the second collection sampling interval.

4. The method of claim 1 , wherein collecting the telemetry data comprises performing, by the performance monitoring system, a pull based collection process to collect the telemetry data.

5. The method of claim 1 , wherein determining the predicted metric weight comprises applying, by the performance monitoring system, a machine learning model to determine the predicted metric weight.

6. The method of claim 1 , wherein determining the predicted metric weight comprises performing, by the performance monitoring system, a regression analysis to determine the predicted metric weight.

7. The method of claim 1 , further comprising updating, by the performance monitoring system, the second collection sampling interval for the first metric on an on-going basis.

8. The method of claim 1 , further comprising determining, by the performance monitoring system, one or more related metrics that are related to the first metric, wherein the metric relevance attribute is based on the access ratio and a group metrics access ratio for the one or more related metrics.

9. A performance monitoring system, comprising:

a memory that stores instructions; and

processing circuitry coupled to the memory that executes the instructions to:

collect telemetry data comprising metrics related to a network of computing devices, wherein, for each metric, metric values associated with a corresponding metric name of the metric are collected at each of a plurality of times according to a first collection sampling interval;

store a query history comprising queries related to the metrics;

generate a metric relevance attribute based on an access ratio determined from a portion of the query history corresponding to a first metric of the metrics;

determine a predicted metric weight for the first metric based on the metric relevance attribute; and

collect additional telemetry data according to a second collection sampling interval for at least one of the metrics, wherein the second collection sampling interval is based on the predicted metric weight for the first metric.

10. The system of claim 9 ,

wherein the second collection sampling interval is different than the first collection sampling interval, and

wherein to collect the additional telemetry data the processing circuitry executes the instructions to collect corresponding metric values for the first metric according to the second collection sampling interval.

11. The system of claim 9 , wherein the processing circuitry further executes the instructions to:

determine whether the first metric is a critical metric; and

based on determining the first metric is a critical metric, use a predetermined minimum sampling interval for the second collection sampling interval.

12. The system of claim 9 , wherein to collect the telemetry data the processing circuitry further executes the instructions to perform a pull based collection process to collect the telemetry data.

13. The system of claim 9 , wherein to determine the predicted metric weight the processing circuitry further executes the instructions to apply a machine learning model to determine the predicted metric weight.

14. The system of claim 9 , wherein to determine the predicted metric weight the processing circuitry further executes the instructions to perform a regression analysis to determine the predicted metric weight.

15. The system of claim 9 , wherein the processing circuitry further executes the instructions to update the second collection sampling interval for the first metric on an on-going basis.

16. The system of claim 9 , wherein the processing circuitry further executes the instructions to determine one or more related metrics that are related to the first metric, wherein the metric relevance attribute is based on the access ratio and a group metrics access ratio for the one or more related metrics.

17. Non-transitory computer-readable storage media comprising instructions, that when executed by processing circuitry of a computing system, cause the processing circuitry to:

collect telemetry data comprising metrics related to a network of computing devices, wherein, for each metric, metric values associated with a corresponding metric name of the metric are collected at each of a plurality of times according to a first collection sampling interval;

store a query history comprising queries related to the metrics;

generate a metric relevance attribute based on an access ratio determined from a portion of the query history corresponding to a first metric of the metrics;

determine a predicted metric weight for the first metric based on the metric relevance attribute; and

collect additional telemetry data according to a second collection sampling interval for at least one of the metrics, wherein the second collection sampling interval is based on the predicted metric weight for the first metric.

18. The non-transitory computer-readable storage media of claim 17 ,

wherein the second collection sampling interval is different than the first collection sampling interval, and

wherein to collect the additional telemetry data the instructions, when further executed by the processing circuitry, cause the processing circuitry to collect corresponding metric values for the first metric according to the second collection sampling interval.

19. The non-transitory computer-readable storage media of claim 17 , wherein the instructions, when further executed by the processing circuitry, cause the processing circuitry to:

determine whether the first metric is a critical metric; and

based on determining the first metric is a critical metric, use a predetermined minimum sampling interval for the second collection sampling interval.

20. The non-transitory computer-readable storage media of claim 17 , wherein the instructions, when further executed by the processing circuitry, cause the processing circuitry to determine one or more related metrics that are related to the first metric, wherein the metric relevance attribute is based on the access ratio and a group metric access ratio for the one or more related metrics.

Assignments (3)
NUNC PRO TUNC ASSIGNMENT Recorded May 6, 2026
From: JUNIPER NETWORKS, INC.
To: HEWLETT PACKARD ENTERPRISE DEVELOPMENT LP
Reel/Frame 075513/0034 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 16, 2025
From: YAVATKAR, RAJENDRA SHIVARAM
To: JUNIPER NETWORKS, INC.
Reel/Frame 073226/0029 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 18, 2025
From: KOMMULA, RAJA; SUNKADA, GANESH BYAGOTI MATAD; SRIDHAR, THAYUMANAVAN; ESWARAN, THIRAVIYA; YAVATKAR, RAJ
To: JUNIPER NETWORKS, INC.
Reel/Frame 072915/0250 →
Priority Claims (1)
IN 202241022566 · Apr 16, 2022 · national
Continuity (2)
Continuation 17810178 · Jun 30, 2022
Related Publication 20240211368A1 · Jun 27, 2024
References Cited (33)
US 7296132B1 · Gross · 2007 [cited by examiner]
US 7522071B2 · Caselli · 2009 [cited by examiner]
US 9571394B1 · Sivaramakrishnan et al. · 2017 [cited by applicant]
US 9749199B2 · Brown · 2017 [cited by examiner]
US 9983968B2 · Gwozdz · 2018 [cited by applicant]
US 10235263B2 · Megahed et al. · 2019 [cited by applicant]
US 10536352B1 · Brisebois et al. · 2020 [cited by applicant]
US 11025521B1 · Neill · 2021 [cited by examiner]
US 11516308B1 · Dubynskiy · 2022 [cited by examiner]
US 20090292954A1 · Jiang et al. · 2009 [cited by applicant]
US 20090306803A1 · Behm · 2009 [cited by examiner]
US 20160124830A1 · Banerjee et al. · 2016 [cited by applicant]
US 20180189163A1 · Megahed et al. · 2018 [cited by applicant]
US 20180241644A1 · Lu · 2018 [cited by applicant]
US 20190114245A1 · Mermoud · 2019 [cited by examiner]
US 20200192741A1 · Estrada et al. · 2020 [cited by applicant]
US 20200356459A1 · Harutyunyan · 2020 [cited by examiner]
US 20200382361A1 · Chandrasekhar et al. · 2020 [cited by applicant]
US 20210149394A1 · Li · 2021 [cited by examiner]
US 20210218619A1 · Harutyunyan · 2021 [cited by examiner]
US 20220121967A1 · Azizsoltani et al. · 2022 [cited by applicant]
US 20230128567A1 · Mermoud · 2023 [cited by examiner]
US 20230229675A1 · Hautyunyan · 2023 [cited by examiner]
US 20230333956A1 · Kommula et al. · 2023 [cited by applicant]
US 20230336408A1 · Kommula et al. · 2023 [cited by applicant]
US 20230336447A1 · Kommula et al. · 2023 [cited by applicant]
CN 109542740A · 2019 [cited by applicant]
WO 2013184846A1 · 2013 [cited by applicant]
Corno et al., “RecRules: Recommending IF-THEN Rules for End-User Development”, ACM Transactions on Intelligent Systems and Technology, vol. 10, No. 5, Sep. 5, 2019, 27 pp. [cited by applicant]
Prosecution History from U.S. Appl. No. 17/810,167, dated Sep. 18, 2023 through Feb. 14, 2024, 38 pp. [cited by applicant]
Prosecution History from U.S. Appl. No. 17/810,178, dated Jun. 23, 2023 through Dec. 12, 2023, 56 pp. [cited by applicant]
Response to Extended Search Report dated Jul. 13, 2023, from counterpart European Application No. 22215171.4 filed Apr. 16, 2024, 13 pp. [cited by applicant]
Notice of Allowance from U.S. Appl. No. 17/810,178 dated May 1, 2024, 8 pp. [cited by applicant]
Cited By (1)
US 12,556,607