Multi-cluster container orchestration
US-2021342193-A1 · Nov 4, 2021 · US
US12430298B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12430298-B2 |
| Application number | US-202318349458-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jul 10, 2023 |
| Priority date | Apr 28, 2021 |
| Publication date | Sep 30, 2025 |
| Grant date | Sep 30, 2025 |
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.
Systems, methods, and storage media provided are useful in a computing environment receiving, modifying, and transforming service level information from database servers and entities in a hosted database environment. Multiple application programming interface (API) calls are made by a database observation system to request information for multiple service level indicators from database servers belonging to multiple different entities. Database observation system receives and aggregates the information for multiple service level indicators from each of the database servers belonging to multiple different entities. The database observation system provides, within a dashboard interface, the aggregated information for each of the multiple service level indicators, individual service level indicator scores, and aggregated service level indicator scores for each of the database servers for each of the multiple entities.
Opening claim text (preview).
The invention claimed is: 1. A method, comprising: causing, by at least one computer processor, multiple application programming interface (API) calls to request information for multiple service level indicators from database servers corresponding respectively to multiple different entities; receiving the information for the multiple service level indicators from each of the database servers corresponding respectively to the multiple different entities; generating, utilizing the at least one computer processor, aggregated information in an electronic storage medium for each of the multiple different entities, the aggregated information comprising the information for the multiple service level indicators from each of the database servers for each of the multiple different entities; providing the aggregated information comprising the information for the multiple service level indicators to a modeling module, wherein the modeling module determines one or more performance impacts that would result from improving one or more service level indicators, of the multiple service level indicators; and receiving, from the modeling module, an action plan for improving the one or more service level indicators, of the multiple service level indicators, the action plan generated by the modeling module based at least in part on a first performance impact, determined by the modeling module, corresponding to improving the one or more service level indicators, of the multiple service level indicators; wherein the multiple service level indicators include two or more of: database backups, uptime production improvements, database storage, block change tracking score, assurance status monitoring score, unused disk storage score, incident free time, uptime, application hangs, average active sessions, and non-critical open incidents; and wherein a configuration associated with at least one of the database servers is modified based on the action plan for improving the one or more service level indicators. 2. The method of claim 1 , further comprising: presenting, within a dashboard interface, the aggregated information for each of the multiple service level indicators for each of the database servers for each of the multiple different entities; receiving, via the dashboard interface provided at a user device, a particular entity; and presenting, within the dashboard interface, the aggregated information for each of the multiple service level indicators for each of the database servers for the particular entity. 3. The method of claim 2 , further comprising: determining, utilizing the at least one computer processor, a service level indicator score for each of the multiple service level indicators for a database server. 4. The method of claim 3 , further comprising: determining, utilizing the at least one computer processor, a first aggregated service level indicator score for the database server by applying a weighted formula to the service level indicator score for each of the multiple service level indicators; and presenting, within the dashboard interface, the first aggregated service level indicator score for the database server. 5. The method of claim 4 , further comprising: determining, utilizing the at least one computer processor, a second aggregated service level indicator score for an entity by averaging the first aggregated service level indicator score for each of the database servers of the entity; and presenting, within the dashboard interface, the second aggregated service level indicator score for the entity. 6. The method of claim 1 , wherein each of the multiple different entities are physically and digitally separate from one another. 7. The method of claim 1 , wherein the multiple service level indicators includes at least one of: downtime and rolling production improvements, or critical open incidents. 8. A system for aggregating service level indicators, the system comprising: a computing device comprising at least one computer processor and at least one computer-storage media; wherein the computing device is configured to perform operations, comprising: causing multiple application programming interface (API) calls to request information for multiple service level indicators from database servers corresponding respectively to multiple different entities; receiving the information for the multiple service level indicators from each of the database servers corresponding respectively to the multiple different entities; generating aggregated information in an electronic storage medium for each of the multiple different entities, the aggregated information comprising the information for the multiple service level indicators from each of the database servers for each of the multiple different entities; providing the aggregated information comprising the information for the multiple service level indicators to a modeling module, wherein the modeling module determines one or more performance impacts that would result from improving one or more service level indicators, of the multiple service level indicators; and receiving, from the modeling module, an action plan for improving the one or more service level indicators, of the multiple service level indicators, the action plan generated by the modeling module based at least in part on a first performance impact, determined by the modeling module, corresponding to improving the one or more service level indicators, of the multiple service level indicators; wherein the multiple service level indicators include two or more of: database backups, uptime production improvements, database storage, block change tracking score, assurance status monitoring score, unused disk storage score, incident free time, uptime, application hangs, average active sessions, and non-critical open incidents; and wherein a configuration associated with at least one of the database servers is modified based on the action plan for improving the one or more service level indicators. 9. The system of claim 8 , wherein the operations further comprise: presenting, within a dashboard interface, the aggregated information for each of the multiple service level indicators for each of the database servers for each of the multiple different entities; receiving, via the dashboard interface provided at a user device, a particular entity; and presenting, within the dashboard interface, the aggregated information for each of the multiple service level indicators for each of the database servers for the particular entity. 10. The system of claim 9 , wherein the operations further comprise: determining a service level indicator score for each of the multiple service level indicators for a database server. 11. The system of claim 10 , wherein the operations further comprise: determining a first aggregated service level indicator score for the database server by applying a weighted formula to the service level indicator score for each of the multiple service level indicators; and presenting, within the dashboard interface, the first aggregated service level indicator score for the database server. 12. The system of claim 11 , wherein the operations further comprise: determining a second aggregated service level indicator score for an entity by averaging the first aggregated service level indicator score for each of the database servers of the entity; and presenting, within the dashboard interface, the second aggregated service level indicator score for the entity. 13. The system of claim 8 , wherein each of the multiple different entities are physically and digitally separate from one another. 14. One
Monitoring arrangements for monitoring the status of the computing system or of the computing system component, e.g. monitoring if the computing system is on, off, available, not available (error or fault processing without redundancy G06F11/0703; error detection or correction by redundancy in data representation G06F11/08; error detection or correction of the data by redundancy in operations G06F11/14; error detection or correction by redundancy in hardware G06F11/16) · CPC title
for performance assessment · CPC title
Performance evaluation by statistical analysis · 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
Design, administration or maintenance of databases · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.