IP Library Granted Patent US 8,214,846
Granted Patent B1
US 8,214,846 · App. 11/854,336 · Granted Jul 3, 2012

Method and system for threshold management

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 8,214,846
App. No.
11/854,336
Granted
Jul 3, 2012
Kind
B1
Abstract

One or more computer-readable media that enable a method of recording object configurations at and after an incident occurs in the object. The present invention captures object configurations surrounding an incident that allows changes to be made in response to the incident to be analyzed. The present invention also may generate an incident classification based on a comparison of the configuration when the incident occurs and after it is resolved.

Claims (51)

1. A non-transitory computer-readable storage media with instructions embodied thereon for performing a method of recording changes made to a queue configuration, the method comprising:

obtaining a first incident message for a queue that communicates that a data volume within the queue has crossed above a threshold,

obtaining a first configuration for the queue when the first incident message is obtained;

obtaining a second incident message for the queue that communicates that the data volume within the queue has returned to a normal value;

obtaining a second configuration for the queue when the second incident message is obtained;

generating an incident classification by comparing the first configuration and the second configuration; and

storing the first configuration, the second configuration, and the incident classification in a data store.

2. The media of claim 1 wherein the queue is a queue in a messaging-middleware application.

3. The media of claim 2 , wherein the queue is a receiving queue.

4. The media of claim 1 , wherein the incident classification indicates whether a setting that triggers the incident message is correct.

5. The media of claim 1 , wherein a basis for the incident classification includes at least one of:

making no queue configuration changes;

adding additional handles;

encountering a problem retrieving data from queue;

encountering a problem writing data to the queue; and

making a change to a queue definition.

6. A non-transitory computer-readable storage media with instructions embodied thereon for performing a method of recording changes made to a queue configuration in response to a status change, the method comprising:

obtaining a first message indicating a queue status has changed to alarm;

obtaining a first configuration for a the queue when the queue status changes to alarm when a data volume within the queue crosses a preset threshold;

obtaining a second message indicating the queue status has returned to normal;

obtaining a second configuration for the queue when the queue status changes to normal when the data volume within the queue crosses from above the preset threshold to below the preset threshold;

generating an incident classification for the status change incident by comparing the first and the second configuration; and

storing the incident classification, the first configuration and the second configuration in a data store.

7. The media of claim 6 , wherein the queue comprises a receiving queue in a messaging-middleware application.

8. The media of claim 6 , wherein the basis for the incident classification is adding additional handles to the queue.

9. The media of claim 8 , wherein the basis for the incident classification includes at least one of:

making no queue configuration changes;

adding additional handles;

encountering a problem retrieving data from a queue;

encountering a problem writing data to the queue; and

making a change to a queue definition.

10. A non-transitory computer-readable storage media with instructions embodied thereon for performing a method of gathering data related to a threshold incident, the method comprising:

monitoring data volume within a queue;

determining that the data volume in the queue crosses a preset-data-volume threshold;

obtaining a first queue configuration when the data volume in the queue crosses the preset-data-volume threshold;

determining that the data volume in the queue returns below the preset data-volume threshold;

obtaining a second queue configuration when the data volume in the queue returns below the preset data-volume threshold;

generating an incident classification of the threshold incident based on a comparison of the first queue configuration and the queue second configuration; and

storing the first queue configuration, the second queue configuration and the incident classification in a data store.

11. The media of claim 10 , wherein the queue is a receiving queue in a messaging-middleware application.

12. The media of claim 10 , wherein the basis for the incident classification includes at least one of:

making no queue configuration changes;

adding additional handles;

encountering a problem retrieving data from a queue;

encountering a problem writing data to the queue; and

making a change to a queue definition.

13. The media of claim 12 , further comprising:

generating a threshold message when basis for the incident classification is making no queue configuration changes, wherein the message references the threshold incident and indicates that the threshold should be evaluated; and

transmitting the threshold message to a system administrator.

14. The media of claim 13 , wherein the first queue configuration, the second queue configuration and the incident classification are stored in a database.

15. The media of claim 14 , wherein the database is a consolidated database that is configured to store the first queue configuration, the second queue configuration and the incident classification for every threshold incident generated by a monitoring solution.

Assignments (5)
RELEASE OF SECURITY INTEREST Recorded Aug 23, 2022
From: DEUTSCHE BANK TRUST COMPANY AMERICAS
To: IBSV LLC; LAYER3 TV, LLC; PUSHSPRING, LLC; T-MOBILE CENTRAL LLC; T-MOBILE USA, INC.; ASSURANCE WIRELESS USA, L.P.; BOOST WORLDWIDE, LLC; CLEARWIRE COMMUNICATIONS LLC; CLEARWIRE IP HOLDINGS LLC; SPRINTCOM LLC; SPRINT COMMUNICATIONS COMPANY L.P.; SPRINT INTERNATIONAL INCORPORATED; SPRINT SPECTRUM LLC
Reel/Frame 062595/0001 →
TERMINATION AND RELEASE OF FIRST PRIORITY AND JUNIOR PRIORITY SECURITY INTEREST IN PATENT RIGHTS Recorded Apr 2, 2020
From: DEUTSCHE BANK TRUST COMPANY AMERICAS
To: SPRINT COMMUNICATIONS COMPANY L.P.
Reel/Frame 052969/0475 →
SECURITY AGREEMENT Recorded Apr 2, 2020
From: T-MOBILE USA, INC.; ISBV LLC; T-MOBILE CENTRAL LLC; LAYER3 TV, INC.; PUSHSPRING, INC.; BOOST WORLDWIDE, LLC; CLEARWIRE COMMUNICATIONS LLC; CLEARWIRE IP HOLDINGS LLC; CLEARWIRE LEGACY LLC; SPRINT COMMUNICATIONS COMPANY L.P.; SPRINT INTERNATIONAL INCORPORATED; SPRINT SPECTRUM L.P.; ASSURANCE WIRELESS USA, L.P.
To: DEUTSCHE BANK TRUST COMPANY AMERICAS
Reel/Frame 053182/0001 →
GRANT OF FIRST PRIORITY AND JUNIOR PRIORITY SECURITY INTEREST IN PATENT RIGHTS Recorded Mar 6, 2017
From: SPRINT COMMUNICATIONS COMPANY L.P.
To: DEUTSCHE BANK TRUST COMPANY AMERICAS
Reel/Frame 041895/0210 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 12, 2007
From: LEONARD, MARK; WASHBURN, BRIAN JOHN; KRISHNAMURTHY, KAILASH
To: SPRINT COMMUNICATIONS COMPANY L.P.
Reel/Frame 019818/0909 →