IP Library Granted Patent US 10,079,715
Granted Patent B1
US 10,079,715 · App. 14/801,485 · Granted Sep 18, 2018

Methods, systems and computer readable mediums for performing metadata-driven data collection

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,079,715
App. No.
14/801,485
Granted
Sep 18, 2018
Kind
B1
Abstract

Methods, systems, and computer readable mediums for performing metadata-driven data collection are disclosed. According to one embodiment, a method for performing metadata-driven data collection includes receiving a request for system related data, wherein the request includes metadata indicating a protocol and identifying information for obtaining the system related data. The method also includes configuring, using the metadata, at least one data collector for obtaining the system related data. The method further includes obtaining, by the at least one data collector, the system related data and storing the system related data in a memory.

Claims (40)

1. A method for performing metadata-driven data collection, the method comprising:

receiving a request for system related data, wherein the request includes metadata indicating identifying information for obtaining the system related data, wherein the identifying information includes a data store identifier;

selecting, using the metadata, at least one data collector from among a plurality of different types of data collectors for gathering information about a system virtual machine (VM);

configuring, using the metadata, the at least one data collector for obtaining the system related data, wherein the at least one data collector is implemented using software executing on at least one processor, where configuring the at least one data collector includes using the metadata to initiate the at least one data collector;

obtaining, by the at least one data collector, the system related data, wherein the at least one data collector accesses, using a simple network management protocol (SNMP) or a storage management initiative (SMI) protocol, a data store identified in the metadata; and

storing the system related data in a memory.

2. The method of claim 1 wherein the metadata includes at least one member selected from a group consisting of a protocol identifier, a namespace identifier, an element type identifier, a field name identifier, a parameter identifier, or a mandatory value flag.

3. The method of claim 1 wherein the request for system related data is received via at least one member selected from a group consisting of a user interface, a graphical user interface (GUI), a command-line interface (CLI), an application programming interface (API), and a representation state transfer (REST) API.

4. The method of claim 1 wherein the at least one data collector includes at least one member selected from a group consisting of a system(s) specific data collector, a component(s) specific data collector, and a protocol(s) specific data collector.

5. The method of claim 1 wherein obtaining, by the at least one data collector, the system related data includes using at least one member selected from a group consisting of an application programming interface (API), a VMWare VSphere API, a REST API, a VNX REST API, and a VNXe REST API.

6. The method of claim 1 comprising:

at least one action selected from a group consisting of:

using the metadata to correlate the system related data collected using different data collectors; and

using the metadata to schedule data collection by the at least one data collector.

7. The method of claim 1 wherein the system related data includes information about at least one member selected from a group consisting of a computing platform, a computing device, a converged infrastructure system, a virtual machine, a hypervisor, a compute component, a network component, a storage component, software, an operating system, firmware, hardware, a physical resource, and a virtual resource.

8. A system for performing metadata-driven data collection, the system comprising:

a processor; and

a data collection engine implemented using the processor, wherein the data collection engine is configured to receive a request for system related data, wherein the request includes metadata indicating identifying information for obtaining the system related data, wherein the identifying information includes a data store identifier, to select, using the metadata, at least one data collector from among a plurality of different types of data collectors for gathering information about a system virtual machine (VM), to configure, using the metadata, the at least one data collector for obtaining the system related data, wherein the at least one data collector is implemented using software executing on at least one processor, where configuring the at least one data collector includes using the metadata to initiate the data collector, to obtain, by the at least one data collector, the system related data, wherein the at least one data collector accesses, using a simple network management protocol (SNMP) or a storage management initiative (SMI) protocol, a data store identified in the metadata, and to store the system related data in a memory.

9. The system of claim 8 wherein the metadata includes at least one member selected from a group consisting of a protocol identifier, a namespace identifier, an element type identifier, a field name identifier, a parameter identifier, or a mandatory value flag.

10. The system of claim 8 wherein the request for system related data is received via at least one member selected from a group consisting of a user interface, a graphical user interface (GUI), a command-line interface (CLI), an application programming interface (API), and a representation state transfer (REST) API.

11. The system of claim 8 wherein the at least one data collector includes at least one member selected from a group consisting of a system(s) specific data collector, a component(s) specific data collector, and a protocol(s) specific data collector.

12. The system of claim 8 wherein the at least one data collector is configured to obtain the system related data using at least one member selected from a group consisting of an application programming interface (API), a VMWare VSphere API, a REST API, a VNX REST API, and a VNXe REST API.

13. The system of claim 8 wherein the data collection engine is configured to perform at least one action selected from a group consisting of:

use the metadata to correlate the system related data collected using different data collectors; and

use the metadata to schedule data collection by the at least one data collector.

14. The system of claim 8 wherein the system related data includes information about at least one member selected from a group consisting of a computing platform, a computing device, a converged infrastructure system, a virtual machine, a hypervisor, a compute component, a network component, a storage component, software, an operating system, firmware, hardware, a physical resource, and a virtual resource.

15. A non-transitory computer readable medium having stored thereon executable instructions which, when executed by a processor of a computer, cause the computer to perform steps comprising:

receiving a request for system related data, wherein the request includes metadata indicating identifying information for obtaining the system related data, wherein the identifying information includes a data store identifier;

selecting, using the metadata, at least one data collector from among a plurality of different types of data collectors for gathering information about a system virtual machine (VM);

configuring, using the metadata, the at least one data collector for obtaining the system related data, wherein the at least one data collector is implemented using software executing on at least one processor, where configuring the at least one data collector includes using the metadata to initiate the at least one data collector;

obtaining, by the at least one data collector, the system related data, wherein the at least one data collector accesses, using a simple network management protocol (SNMP) or a storage management initiative (SMI) protocol, a data store identified in the metadata; and

storing the system related data in a memory.

16. The non-transitory computer readable medium of claim 15 wherein the metadata includes at least one member selected from a group consisting of a protocol identifier, a namespace identifier, an element type identifier, a field name identifier, a parameter identifier, or a mandatory value flag.

17. The non-transitory computer readable medium of claim 15 wherein the request for system related data is received via at least one member selected from a group consisting of a user interface, a graphical user interface (GUI), a command-line interface (CLI), an application programming interface (API), and a representation state transfer (REST) API.

18. The non-transitory computer readable medium of claim 15 wherein the at least one data collector includes at least one member selected from a group consisting of a system(s) specific data collector, a component(s) specific data collector and a protocol(s) specific data collector.

19. The non-transitory computer readable medium of claim 15 wherein obtaining, by the at least one data collector, the system related data includes using at least one member selected from a group consisting of, an application programming interface (API), a VMWare VSphere API, a REST API, a VNX REST API, and a VNXe REST API.

20. The non-transitory computer readable medium of claim 15 comprising:

at least one action selected from a group consisting of:

using the metadata to correlate the system related data collected using different data collectors; and

using the metadata to schedule data collection by the at least one data collector.

Assignments (6)
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (053546/0001) Recorded Jun 23, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.); DELL INTERNATIONAL L.L.C.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.); EMC IP HOLDING COMPANY LLC
Reel/Frame 071642/0001 →
SECURITY AGREEMENT Recorded Apr 22, 2020
From: CREDANT TECHNOLOGIES INC.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; FORCE10 NETWORKS, INC.; WYSE TECHNOLOGY L.L.C.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 053546/0001 →
MERGER Recorded Mar 26, 2020
From: VCE IP HOLDING COMPANY LLC
To: EMC IP HOLDING COMPANY LLC
Reel/Frame 052236/0497 →
SECURITY AGREEMENT Recorded Mar 21, 2019
From: CREDANT TECHNOLOGIES, INC.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; FORCE10 NETWORKS, INC.; WYSE TECHNOLOGY L.L.C.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 049452/0223 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 8, 2016
From: VCE COMPANY, LLC
To: VCE IP HOLDING COMPANY LLC
Reel/Frame 040576/0161 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 22, 2015
From: NANDYALAM, RAJESH; MADHIPATLA, VENKATESH SUDARSANAM; PENG, BAYI; FU, XIAOHONG; BOURNE, GEOFFREY DAVID
To: VCE COMPANY, LLC
Reel/Frame 036155/0903 →