# US 2022/0012096 A1 · Resource determination based on resource definition data

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2022/0012096 A1
- Document ID: US20220012096A1
- Status: Published application
- Kind: A1
- Application number: 17/001,711
- Filed: 2020-08-25
- Published: 2022-01-13
- Earliest claimed: 2020-07-11
- Assignees: VMware, Inc.
- Applicants: Vmware, Inc.
- Inventors: VIPUL CHAUDHARY; Sandeep L. Hegde; Shyam Venkatram; Naren Lal; Ranganathan Srinivasan
- Web page: https://patentgrep.com/patent/US20220012096A1

## CPC

- G06F 9/5027: {the resource being a machine, e.g. CPUs, Servers, Terminals}
- G06F 11/3051: {Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs (verification or detection of system hardware configuration G06F11/2247)}
- G06F 9/54: Interprogram communication
- G06F 11/302: {where the computing system component is a software system}
- G06F 16/288: {Entity relationship models}
- G06F 2201/865: Monitoring of software
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

In one example, a computer implemented method may include retrieving resource definition data corresponding to an endpoint. The resource definition data includes resource type information. Further, an API response may be obtained from the endpoint by querying the endpoint using an API call. Furthermore, the API response may be parsed and a resource model corresponding to the resource definition data may be populated using the parsed API response. The resource model may include resource information and associated metric information correspond to a resource type in the resource type information. Further, a resource and/or metric data associated with the resource may be determined using the populated resource model. The resource may be associated with an application being executed in the endpoint.

## Claims

### Claim 1

A computer implemented method comprising:
retrieving resource definition data corresponding to an endpoint, wherein the resource definition data comprises resource type information;
obtaining an API response from the endpoint by querying the endpoint using an application program interface (API) call;
parsing the API response obtained from the endpoint;
populating a resource model corresponding to the resource definition data using the parsed API response, wherein the resource model comprises resource information and associated metric information corresponding to a resource type in the resource type information; and
determining a resource and/or metric data associated with the resource using the populated resource model, wherein the resource is associated with an application being executed in the endpoint.

### Claim 2 (depends on 1)

The computer implemented method of claim 1, further comprising:
presenting the determined resource and/or the metric data associated with the resource on a graphical user interface.

### Claim 3 (depends on 1)

The computer implemented method of claim 1, further comprising:
populating a relationship model corresponding to the resource definition data using the parsed API response, wherein the relationship model corresponds to the resource type;
determining a relationship of the resource with another resource using the populated relationship model; and
presenting the relationship on a graphical user interface.

### Claim 4 (depends on 1)

The computer implemented method of claim 1, wherein obtaining the API response comprises:
generating a thread corresponding to the resource type; and
executing the thread to:
query the endpoint by making the API call; and
obtain the API response in response to the query.

### Claim 5 (depends on 4)

The computer implemented method of claim 4, further comprising:
validating transformation definitions in the resource definition data against a predefined transformation schema prior to generating the thread.

### Claim 6 (depends on 1)

The computer implemented method of claim 1, wherein populating the resource model corresponding to the resource definition data comprises:
populating the resource information of the resource model in the resource definition data with the parsed API response; and
applying transformation rules defined in the resource definition data to the parsed API response and/or the populated resource information to populate the metric information of the resource model.

### Claim 7 (depends on 6)

The computer implemented method of claim 6, further comprising:
validating values in the parsed API response; and
populating the resource model in the resource definition data using the parsed API response upon a successful validation.

### Claim 8 (depends on 1)

The computer implemented method of claim 1, wherein the resource definition data is included in a computer readable data structure, and wherein the computer readable data structure is formatted in accordance with one or more of JavaScript object notation (JSON), extensible markup language (XML), a binary file, a database file, YAML ain't markup language (YAML), and/or a proprietary encoding scheme.

### Claim 9 (depends on 1)

The computer implemented method of claim 1, wherein the resource definition data comprises an API call address to make the API call to the endpoint.

### Claim 10 (depends on 1)

The computer implemented method of claim 1, wherein the resource definition data comprises a reference to an API call address that is located in an external source, wherein the API call address is used to make the API call to the endpoint.

### Claim 11 (depends on 1)

The computer implemented method of claim 1, wherein the endpoint comprises a collection of servers and applications that work together at a production phase, the applications being accessible to one or more users.

### Claim 12

A management node comprising:
an adapter to communicate with an endpoint, the adapter comprising:
a resource transformer to:
retrieve resource definition data corresponding to the endpoint, wherein the resource definition data comprises resource type information; and
a resource manager to:
obtain a plurality of API responses from the endpoint by querying the endpoint using an application program interface (API) call;
parse the API responses obtained from the endpoint; and
populate a plurality of resource models corresponding to the resource definition data using the parsed API responses, wherein each of the resource models comprises resource information and associated metric information that correspond to a resource type in the resource type information; and
a resource extractor to:
determine a plurality of resources and/or metric data associated with the resources using the populated resource models.

### Claim 13 (depends on 12)

The management node of claim 12, wherein the resource extractor is to:
present the plurality of resources and/or the metric data associated with the plurality of resources on a graphical user interface, wherein the resources are associated with one or more applications being executed in the endpoint.

### Claim 14 (depends on 12)

The management node of claim 12, wherein the resource extractor is to:
populate a relationship model corresponding to the resource definition data using the parsed API responses, wherein the relationship model corresponds to the resource type;
determine a relationship between the plurality of resources using the populated relationship model;
generate a resource topology corresponding to the endpoint using the determined relationship between the plurality of resources; and
present the generated resource topology on a graphical user interface.

### Claim 15 (depends on 12)

The management node of claim 12, wherein the resource manager is to:
generate a thread pool with each thread in the thread pool corresponding to a resource type in the resource definition data; and
execute the thread pool such that each thread is to obtain a corresponding API response by querying the endpoint by making the API call.

### Claim 16 (depends on 12)

The management node of claim 12, wherein the resource manager is to:
populate the resource information of the plurality of resource models in the resource definition data with the parsed plurality of API responses; and
apply transformation rules defined in the resource definition data to the parsed plurality of API responses and/or the plurality of populated resource information to populate the metric information.

### Claim 17 (depends on 12)

The management node of claim 12, wherein the endpoint comprises one of a physical computing environment, a cloud computing environment, and a virtual computing environment.

### Claim 18

A non-transitory machine-readable storage medium encoded with instructions that, when executed by a computing device, cause the computing device to:
retrieve resource definition data corresponding to an endpoint from an adapter of the computing device, wherein the adapter is to enable communication with the endpoint, and wherein the resource definition data comprises resource type information;
generate a thread corresponding to a resource type in the resource type information;
execute the thread to obtain an API response by querying the endpoint using an application program interface (API) call;
parse the API response obtained from the endpoint;
populate a resource model corresponding to the resource definition data using the parsed API response, wherein the resource model comprises resource information and associated metric information corresponding to the resource type; and
store the populated resource model in a memory.

### Claim 19 (depends on 18)

The non-transitory machine-readable storage medium of claim 18, further comprising instructions that, when executed by the processor, cause the processor to:
determine a resource and/or metric data using the populated resource model in the memory, wherein the resource is associated with an application being executed in the endpoint.

### Claim 20 (depends on 18)

The non-transitory machine-readable storage medium of claim 18, wherein instructions to populate the resource model comprise instructions to:
convert the parsed API response in a form of the resource model defined in the resource definition data.

### Claim 21 (depends on 18)

The non-transitory machine-readable storage medium of claim 18, wherein the resource definition data comprises an API call address to make the API call to the endpoint.

### Claim 22 (depends on 18)

The non-transitory machine-readable storage medium of claim 18, wherein the resource definition data comprises a reference to an API call address that is located in an external source, wherein the API call address is used to make the API call to the endpoint.
