IP Library Granted Patent US 10,735,246
Granted Patent B2
US 10,735,246 · App. 15/110,938 · Granted Aug 4, 2020

Monitoring an object to prevent an occurrence of an issue

Inventors: Roberto Antonio Contreras Masse (Ciudad Juarez, MX); Rong Pan (Sunnyvale, CA); Rajesh Dontula (Irving, TX); Dong Han (Shanghai, CN); Jun Wang (Shanghai, CN); Guo-Xiang Qin (Shanghai, CN); Easwaran Nadhan (Downers Grove, IL)
Assignee: ENT. SERVICES DEVELOPMENT CORPORATION LP
H04L41/065H04L41/046H04L41/069H04L41/0654H04L43/16H04L63/1408H04L63/20
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 10,735,246
App. No.
15/110,938
Granted
Aug 4, 2020
Kind
B2
Abstract

Monitoring an object to prevent an occurrence of an issue includes monitoring an object based on a number of parameters, categorizing messages of the object into categories while monitoring for a recurrence of a pattern of messages, detecting a potential issue with the object based on the recurrence of the pattern of messages, and alerting an operations manager agent of the potential issue to prevent an occurrence of the issue.

Claims (36)

1. A method comprising:

monitoring an application component based on a number of parameters;

categorizing messages of the application component into categories;

detecting and analyzing patterns of messages that occur in the messages of the application component, wherein each of the patterns of messages is a sequence of the categories in an order;

monitoring how many times each of the patterns of messages occurs in the messages of the application component within a predetermined time period;

detecting an issue with the application component based on the order of the categories in the sequence and a number of the order occurring more than a predetermined number of times within the predetermined time period;

alerting an operations manager agent of the issue to prevent an occurrence of the issue; and

instantiating a remediation function for remediating the issue based on policies of the operations manager agent, wherein the policies indicate execution of a script on an object to restore service to the object.

2. The method of claim 1 , in which monitoring the application component based on the number of parameters comprises:

receiving the messages from the application component; and

interrogating the application component for performance, availability, resources, or combinations thereof.

3. The method of claim 1 , in which the detecting the issue with the application component further comprises, for each of the patterns of messages, comparing the number of times a respective pattern of messages has occurred within a time period with a threshold parameter.

4. The method of claim 3 , in which the threshold parameter comprises a specific number of times the respective pattern of the messages can reoccur over the time period.

5. The method of claim 1 , in which categorizing messages of the application component into categories based on a recurrence of a pattern of the messages comprises categorizing a message of the application component that is a resource message into a resource messages category, a message of the application component that is a performance message into a performance messages category, a message of the application component that is an availability message into an availability message category, or combinations thereof.

6. The method of claim 1 , in which the number of parameters comprises a monitoring frequency parameter, threshold parameters, performance parameters, availability parameters, resource parameters, location parameters, log file parsing parameters, or combinations thereof.

7. A system for monitoring an application component to prevent an occurrence of an issue, the system comprising:

at least one processor; and

a memory storing instructions that, when executed by the at least one processor, cause the system to:

monitor the application component based on a number of parameters;

categorize messages received from the application component into categories;

detect and analyze patterns of messages that occur in the messages received from the application component, wherein each of the patterns of messages is a sequence of the categories in an order;

detect the issue with the application component by determining the order of the categories in the sequence occurs with respective categories associated with the messages of the application component and a number of times the order occurs within a predetermined period of time;

alert an operations manager agent of the issue to prevent the occurrence of the issue; and

instantiate a remediation function for remediating the issue based on policies of the operations manager agent, wherein the policies indicate an execution of a script on an object to restore service to the object.

8. The system of claim 7 , in which the instructions further cause the system to categorize a message of the application component that is a resource message into a resource messages category, a message of the application component that is a performance message into a performance messages category, a message of the application component that is an availability message into an availability message category, or combinations thereof.

9. The system of claim 7 , in which the instructions further cause the system to, for each of the patterns of messages, compare the number of times a respective pattern of messages occurs in the messages of the application component within the predetermined period of time with a threshold parameter.

10. The system of claim 7 , in which the number of parameters comprises a monitoring frequency parameter, a threshold parameter, performance parameters, availability parameters, resource parameters, location parameters, log file parsing parameters, or combinations thereof.

11. A computer program product for monitoring an application component to prevent an occurrence of an issue, comprising:

a non-transitory computer readable storage medium, said non-transitory computer readable storage medium comprising computer readable program code embodied therewith, said computer readable program code comprising program instructions that, when executed, causes a processor to:

monitor the application component based on a number of parameters;

categorize the messages received from the application component into categories;

detect and analyze patterns of messages in messages received from the application component, wherein each of the patterns of messages is a sequence of the categories in an order;

monitor how many times each of the patterns of messages occurs in the messages of the application component within a predetermined period of time;

detect the issue with the application component based on that the order of the categories in the sequence occurs with respective categories associated with the messages and that a number of occurrences of the order is more than a predetermined number of times within the predetermined period of time

alert an operations manager agent of the issue to prevent the occurrence of the issue; and

instantiate a remediation function for remediating the issue based on policies of the operations manager agent, wherein the policies indicate an execution of a script on an object to restore service to the object.

Assignments (3)
NUNC PRO TUNC ASSIGNMENT Recorded Jun 7, 2017
From: HEWLETT PACKARD ENTERPRISE DEVELOPMENT LP
To: ENT. SERVICES DEVELOPMENT CORPORATION LP
Reel/Frame 042625/0512 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 12, 2016
From: CONTRERAS MASSE, ROBERTO ANTONIO; PAN, RONG; DONTULA, RAJESH; HAN, DONG; WANG, JUN; QIN, GUO-XIANG; NADHAN, EASWARAN
To: HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P.
Reel/Frame 039127/0961 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 12, 2016
From: HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P.
To: HEWLETT PACKARD ENTERPRISE DEVELOPMENT LP
Reel/Frame 039313/0001 →
Continuity (1)
Related Publication 20160344583A1 · Nov 24, 2016