Application monitoring for cloud-based architectures
US-9819729-B2 · Nov 14, 2017 · US
US11720406B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11720406-B2 |
| Application number | US-202117304231-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jun 16, 2021 |
| Priority date | Dec 5, 2019 |
| Publication date | Aug 8, 2023 |
| Grant date | Aug 8, 2023 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A cloud capacity system enables calculation and tracking of cloud capacity metrics for data center pods. The system includes a “Cloud Capacity Snapshot” table having a number of different cloud capacity columns; a “Cloud Capacity Query” table that stores a respective, customizable query for each of the cloud capacity columns defining criteria for selecting and combining data to calculate the corresponding cloud capacity metric value; and a “Cloud Capacity URLs” table that stores cloud capacity universal resource locator (URLs). Each cloud capacity URL embodies or encodes a respective cloud capacity query of the “Cloud Capacity Query” table for a given combination of a particular cloud capacity column and a particular pod in the “Cloud Capacity Snapshot” table. As such, by executing the queries encoded in the “Cloud Capacity URLs” table, each cloud capacity field of the “Cloud Capacity Snapshot” table is populated with the corresponding cloud capacity metric value.
Opening claim text (preview).
The invention claimed is: 1. A system hosted by a data center having a plurality of pods, the system comprising: at least one memory configured to store a metrics table and a queries table, wherein the metrics table includes a column configured to store a respective metric value for each of the plurality of pods of the data center; and at least one processor configured to execute instructions stored in the at least one memory to perform actions comprising: selecting a query from the queries table, wherein the query is associated with the column of the metrics table; and for each pod of the plurality of pods of the data center: generating a uniform resource locator (URL) that encodes the query to calculate the respective metric value for the pod of the data center; accessing the URL to execute the encoded query and, in response, receiving the respective metric value for the pod of the data center; and updating the column of the metrics table to include the respective metric value for the pod of the data center. 2. The system of claim 1 , wherein the metrics table includes a first pod identifier column configured to store a respective pod identifier value for each of the plurality of pods of the data center. 3. The system of claim 2 , wherein the at least one memory is configured to store a URL table that includes a second pod identifier column configured to store the respective pod identifier value for each of the plurality of pods of the data center, wherein the metrics table and the URL table are related by the first pod identifier column and the second pod identifier column. 4. The system of claim 3 , wherein the queries table includes a name column configured to store a name of the column of the metrics table. 5. The system of claim 4 , wherein the name column is a first name column, wherein the URL table includes a second name column configured to store the name of the column of the metrics table, wherein the queries table and the URL table are related by the first name column and the second name column. 6. The system of claim 1 , wherein the query comprises: filter criteria including at least one parameter of a database table, at least one comparison operator, and at least one value; a combination operation column that indicates a particular column of the database table that is combined to calculate the respective metric value; and a combination operation that indicates how values in the particular column of the database table are combined to calculate the respective metric value. 7. The system of claim 6 , wherein the combination operation comprises summing the values in the particular column, counting the values in the particular column, determining a minimum value in the particular column, determining a maximum value in the particular column, or determining an average of the values in the particular column of the database table. 8. The system of claim 6 , wherein the at least one processor is configured to execute the instructions stored in the at least one memory to perform actions comprising: storing the URL in a URL table in the at least one memory, wherein the URL encodes the filter criteria, the combination operation column, the combination operation, and an identity of the pod. 9. The system of claim 6 , wherein the system includes a graphical user interface (GUI) comprising user input mechanisms configured to enable a user to visually construct the filter criteria of the query. 10. The system of claim 1 , wherein the at least one memory is configured to store an archive table, and wherein the at least one processor is configured to execute the instructions stored in the at least one memory to perform actions comprising: before updating the column of the metrics table, adding the respective metric value of each of the plurality of pods of the data center to the archive table. 11. The system of claim 1 , wherein the queries table includes at least one audit field configured to store audit information related to data modifications within the queries table. 12. A method, comprising: selecting a plurality of queries from a queries table, wherein each of the plurality of queries is associated with a respective column of a metrics table, and each respective column is configured to store a respective metric value for each of a plurality of pods of a data center; and for each query of the plurality of queries: for each pod of the plurality of pods of the data center: generating a uniform resource locator (URL) that encodes the query to calculate the respective metric value for the pod of the data center; accessing the URL to execute the encoded query and, in response, receiving the respective metric value for the pod of the data center; and updating the column of the metrics table to include the respective metric value for the pod of the data center. 13. The method of claim 12 , comprising determining a respective name of each respective column of the metrics table, and wherein selecting the plurality of queries from the queries table comprises: selecting the plurality of queries from the queries table based on the respective name of each respective column of the metrics table. 14. The method of claim 12 , wherein selecting the plurality of queries is triggered by a scheduled job hosted by the data center. 15. The method of claim 12 , comprising: before selecting the plurality of queries, receiving user input from a graphical user interface (GUI), and in response, modifying at least one query of the plurality of queries stored in the queries table based on the received user input. 16. The method of claim 15 , wherein selecting the plurality of queries is triggered by the modifying of the at least one query of the plurality of queries. 17. The method of claim 12 , wherein updating the respective column comprises: storing the respective metric value for the pod of the data center as a numerical value in the respective column of the metrics table. 18. The method of claim 12 , wherein updating the respective column comprises: storing a snapshot URL in the respective column for the pod of the data center, wherein the snapshot URL has a name that is the respective metric value for the pod of the data center, and the snapshot URL refers to a second query that includes filter criteria of the query. 19. One or more tangible, non-transitory, computer-readable media at least collectively storing instructions executable by at least one processor of a data center having a plurality of pods, wherein the instructions include instructions to: select, from a queries table, a query associated with a column of a metrics table, wherein the column of the metrics table is configured to store a respective metric value for each pod of the plurality of pods of the data center; and for each pod of the plurality of pods of the data center: generate a uniform resource locator (URL) that encodes the query to calculate the respective metric value for the pod of the data center; access the URL to execute the encoded query and, in response, receiving the respective metric value for the pod of the data center; and update the column of the metrics table to include the respective metric value for the pod of the data center. 20. The media of claim 19 , wherein the column of the metrics table is a first column, and wherein the instructions comprise instructions to: select a second query from the queries table, wherein the second query corresponds to a second column of the metrics table, and the second colum
the resource being a machine, e.g. CPUs, Servers, Terminals · CPC title
Execution arrangements for user interfaces · CPC title
Techniques for rebalancing the load in a distributed system · CPC title
where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems (multiprogramming arrangements G06F9/46; allocation of resources G06F9/50) · CPC title
Resource availability · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.