IP Library › Granted Patent US 10,261,945

Granted Patent B1

US 10,261,945 · App. 14/613,917 · Granted Apr 16, 2019

Systems and methods for storing and accessing monitoring data

Inventors: Aaron Blackwell (Redding, CT); Matthew L. Domsch (Austin, TX); Michael J. Morton (Morrisville, NC); Charles Terrence Perusse (Pflugerville, TX); James T. Ahlborn (Downingtown, PA)

Assignee: Quest Software Inc.

G06F16/13

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,261,945
App. No.: 14/613,917
Filed: Feb 4, 2015
Granted: Apr 16, 2019
Kind: B1
Examiner: HO, ANDREW N
Art Unit: 2162
USPC: 707/821

External Links

USPTO Patent Center↗ Full Patent PDF↗

Abstract

In one embodiment, a method includes receiving a request for a value of at least one data element defined by a master data management (MDM) model, wherein the at least one data element is based, at least in part, on monitoring data collected from a monitored system. The method further includes determining from a central data store whether the at least one data element is centrally stored or is federated. The central data store maintains a common representation of a plurality of data elements in conformance to the MDM model. The MDM model is extended to indicate whether each data element of the plurality of data elements is centrally stored or is federated. The determining is based, at least in part, on the indication.

Claims (89)

1. A method comprising, by a computer system:

receiving a request for a value of at least one data element defined by a master data management (MDM) model, wherein the at least one data element is based, at least in part, on monitoring data collected from a monitored system;

determining from a central data store whether the at least one data element is centrally stored or is federated;

wherein the central data store maintains a common representation of a plurality of data elements in conformance to the MDM model;

wherein the MDM model is extended to include a storage-location scheme that indicates whether each data element of the plurality of data elements is:

centrally stored such that values of the data element are centrally stored in the central data store in addition to being locally stored on a respective local data store; or

federated such that the values of the data element are locally stored in the respective local data store and are not centrally stored in the central data store, and such that a location identifier of the values in the respective local data store is stored in the central data store;

wherein, for each data element of the plurality of data elements, the indication is based on a previous automatic implementation of the storage-location scheme, the automatic implementation comprising:

automatically analyzing the data element against automated criteria associated with the storage-location scheme;

responsive to a determination, based at least partly on the automatic analysis, of central storage for the data element, indicating in the central data store that the data element is centrally stored, such that the values of the data element are centrally stored in the central data store in addition to being locally stored in the respective local data store; and

responsive to a determination, based at least partly on the automatic analysis, of federated storage for the data element, indicating in the central data store that the data element is federated, such that the values of the data element are not centrally stored in the central data store, and such that a location identifier of the values in the respective local data store is stored in the central data store;

wherein the determining is based, at least in part, on the indication;

responsive to a determination that the at least one data element is federated, retrieving the value of the at least one data element from a federated storage location;

determining based, at least in part, on the retrieved value of the at least one data element from the federated storage location, that the at least one data element be identified as centrally stored;

responsive to the determining that the at least one data element be identified as centrally stored, modifying the storage-location scheme to indicate that the values of the at least one data element are centrally stored in the central data store in addition to being locally stored on the respective local data store; and

providing data related to the value of the at least one data element to a requestor.

2. The method of claim 1 , wherein the central data store stores a reference to the federated storage location.

3. The method claim 1 , wherein:

the automatic analysis comprises a determination of whether each data element is a derived metric; and

for each derived metric, the central data store includes a central-storage indicator.

4. The method claim 1 , wherein:

the automatic analysis comprises a determination of how often the at least one data element is needed based, at least in part, on an automated review of a reporting schedule;

for data elements needed more frequently than a threshold frequency, the central data store includes a central-storage indicator; and

for data elements not needed more frequently than the threshold frequency, the central data store includes a federated-storage indicator.

5. The method of claim 1 , wherein:

the automatic analysis comprises a complexity evaluation of the at least one data element;

for data elements satisfying a complexity threshold, the central data store includes a central-storage indicator; and

for data elements not satisfying the complexity threshold, the central data store includes a federated-storage indicator.

6. The method of claim 1 , wherein the automatic analysis comprises an analysis of each data element of a plurality of data elements based on a combination of criteria comprising: whether the data element is a derived metric, a frequency at which the data element is needed, and a complexity of obtaining the data element.

7. The method of claim 1 , comprising:

periodically pre-fetching, from a plurality of federated locations, values of data elements that are indicated in the central data store to be centrally stored; and

storing the pre-fetched values in the central data store.

8. The method of claim 1 , comprising:

periodically receiving, without requesting, values of data elements that are indicated in the central data store to be centrally stored;

wherein the received values are received from a plurality of federated storage locations; and

storing the received values in the central data store.

9. The method of claim 1 , wherein:

the at least one data element is a derived metric from one or more other data elements;

the federated storage location comprises a cache on a federated computer system; and

the federated computer system computes the derived metric and stores the derived metric in the cache.

10. The method of claim 1 , wherein the indication in the central data store is selected from the group consisting of: a tag of centrally-stored data elements, a tag of federated data elements, and a separate indicator for each data element.

11. An information handling system comprising at least one processor, wherein the at least one processor is operable to implement a method comprising: