# US 12,602,289 B1 · Systems and methods for preventing gray failures in cloud applications > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,602,289 B1 - Document ID: US12602289B1 - Status: Granted - Kind: B1 - Application number: 18/950,541 - Filed: 2024-11-18 - Granted: 2026-04-14 - Earliest claimed: 2024-11-18 - Assignees: JPMorgan Chase Bank, N.A. - Applicants: Jpmorgan Chase Bank, N.A. - Inventors: Ashish Lamichhane; Kiran Sekharamahanthi; Allie Pistolessi; Robert Huarcaya Lazaro - Web page: https://patentgrep.com/patent/US12602289B1 ## CPC - G06F 9/5083: {Techniques for rebalancing the load in a distributed system} - G06F 11/142: {Reconfiguring to eliminate the error (group management mechanisms in a peer-to-peer network H04L67/1044)} - G06F 9/5072: {Grid computing} - H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract A method may include: a listener application receiving a health status of cloud applications in cloud pools, each cloud pool hosted by cloud hardware; the listener application receiving a maintenance schedule comprising a plurality of maintenance events for the cloud application and/or the cloud hardware, the maintenance schedule; the listener application identifying an impacted cloud application and/or cloud hardware that is scheduled for one of the maintenance events; the listener application mapping the impacted cloud hardware and/or cloud applications to a global load balancer; a remediation application sending a first command to the mapped global load balancer to disable traffic to the impacted cloud hardware and/or cloud applications; the remediation application executing the maintenance events on the cloud hardware and/or cloud applications; the remediation application sending a second command to the global mapped global load balancer to re-enable traffic to the impacted cloud hardware and/or cloud applications. ## Claims ### Claim 1 A method, comprising: receiving, by a listener application and from a health monitoring application for a plurality of cloud pools, a health status of a plurality of cloud applications in the plurality of cloud pools, each cloud pool hosted by cloud hardware; receiving, by the listener application, a maintenance schedule for the plurality of cloud applications and/or the cloud hardware, the maintenance schedule comprising a plurality of maintenance events; identifying, by the listener application, an impacted cloud application of the plurality of cloud applications and/or impacted cloud hardware that is scheduled for one of the plurality of maintenance events from the maintenance schedule; mapping, by the listener application, the impacted cloud hardware and/or the impacted cloud application to a global load balancer; sending, by a remediation application, a first command to the mapped global load balancer to disable traffic to the impacted cloud hardware and/or the impacted cloud application; executing, by the remediation application, the maintenance events on the impacted cloud hardware and/or the impacted cloud application; and sending, by the remediation application, a second command to the mapped global load balancer to re-enable traffic to the impacted cloud hardware and/or the impacted cloud application. ### Claim 2 (depends on 1) The method of claim 1, wherein each of the plurality of cloud pools comprises an instance of each cloud application. ### Claim 3 (depends on 1) The method of claim 1, further comprising: receiving, by the listener application, critical resource utilization and terminate signals from the plurality of cloud pools. ### Claim 4 (depends on 1) The method of claim 1, wherein the health monitoring application periodically polls the cloud hardware and/or the plurality of cloud applications for a health status. ### Claim 5 (depends on 1) The method of claim 1, wherein the maintenance events comprise patches. ### Claim 6 (depends on 1) The method of claim 1, further comprising: determining, by the remediation application, that the impacted cloud hardware and/or the impacted cloud application can be taken out of scope before sending the first command. ### Claim 7 (depends on 6) The method of claim 6, wherein the determination is based on a degradation in service resulting from the impacted cloud hardware and/or the impacted cloud application being taken out of scope. ### Claim 8 (depends on 1) The method of claim 1, further comprising: retrieving, by the listener application, a prior status of the cloud hardware and/or the plurality of cloud applications; and determining, by the listener application, that the impacted cloud hardware and/or the impacted cloud application were previously healthy before identifying the impacted cloud application and/or the impacted cloud hardware. ### Claim 9 (depends on 1) The method of claim 1, wherein the remediation application waits a period of time before sending the second command. ### Claim 10 A system, comprising: a plurality of cloud pools, each cloud pool hosted by cloud hardware; a plurality of cloud applications in each of the plurality of cloud pools; a health monitoring application for the plurality of cloud applications in each of the plurality of cloud pools; a plurality of global load balancers, each load balancer in communication with a subset of the plurality of cloud pools; a listener application; and a remediation application; wherein: the listener application is configured to receive, from each health monitoring application, a health status of the plurality of cloud applications in the plurality of cloud pools; the listener application is configured to receive a maintenance schedule for the plurality of cloud applications and/or the cloud hardware, the maintenance schedule comprising a plurality of maintenance events; the listener application is configured to identify an impacted cloud application of the plurality of cloud applications and/or impacted cloud hardware that is scheduled for one of the plurality of maintenance events from the maintenance schedule; the listener application is configured to map the impacted cloud hardware and/or the impacted cloud application to a global load balancer; the remediation application is configured to send a first command to the mapped global load balancer to disable traffic to the impacted cloud hardware and/or the impacted cloud application; the mapped global load balancer is configured to disable traffic to the impacted cloud hardware and/or the impacted cloud application; the remediation application is configured to execute the maintenance events on the impacted cloud hardware and/or the impacted cloud application; the remediation application is configured to send a second command to the global load balancer to re-enable traffic to the impacted cloud hardware and/or the impacted cloud application; and the mapped global load balancer is configured to enable traffic to the impacted cloud hardware and/or the impacted cloud application. ### Claim 11 (depends on 10) The system of claim 10, wherein each of the plurality of cloud pools comprises an instance of each cloud application. ### Claim 12 (depends on 10) The system of claim 10, wherein the listener application is configured to receive critical resource utilization and terminate signals from the plurality of cloud pools. ### Claim 13 (depends on 10) The system of claim 10, wherein the health monitoring application periodically polls the cloud hardware and/or the plurality of cloud applications for a health status. ### Claim 14 (depends on 10) The system of claim 10, wherein the maintenance events comprise patches. ### Claim 15 (depends on 10) The system of claim 10, wherein the remediation application is configured to determine that the impacted cloud hardware and/or the impacted cloud application can be taken out of scope before sending the first command, wherein the determination is based on a degradation in service resulting from the impacted cloud hardware and/or the impacted cloud application being taken out of scope. ### Claim 16 (depends on 10) The system of claim 10, wherein: the listener application is configured to receive a prior status of the cloud hardware and/or the plurality of cloud applications; and the listener application is configured to determine that the impacted cloud hardware and/or the impacted cloud application were previously healthy before identifying the impacted cloud application and/or the impacted cloud hardware. ### Claim 17 (depends on 10) The system of claim 10, wherein the remediation application waits a period of time before sending the second command. ### Claim 18 A non-transitory computer readable storage medium, including instructions stored thereon, which when read and executed by one or more computer processors, cause the one or more computer processors to perform steps comprising: receiving, from a health monitoring application for a plurality of cloud pools, a health status of a plurality of cloud applications in the plurality of cloud pools, each cloud pool hosted by cloud hardware, wherein each of the plurality of cloud pools comprises an instance of each cloud application; receiving a maintenance schedule for the plurality of cloud applications and/or the cloud hardware, the maintenance schedule comprising a plurality of maintenance events; identifying an impacted cloud application of the plurality of cloud applications and/or impacted cloud hardware that is scheduled for one of the plurality of maintenance events from the maintenance schedule; mapping the impacted cloud hardware and/or the impacted cloud application to a global load balancer; sending a first command to the mapped global load balancer to disable traffic to the impacted cloud hardware and/or the impacted cloud application; executing the maintenance events on the impacted cloud hardware and/or the impacted cloud application; and sending a second command to the mapped global load balancer to re-enable traffic to the impacted cloud hardware and/or the impacted cloud application. ### Claim 19 (depends on 18) The non-transitory computer readable storage medium of claim 18, further including instructions stored thereon, which when read and executed by the one or more computer processors, cause the one or more computer processors to perform steps comprising: determining that the impacted cloud hardware and/or the impacted cloud application can be taken out of scope before sending the first command, wherein the determination is based on a degradation in service resulting from the impacted cloud hardware and/or the impacted cloud application being taken out of scope. ### Claim 20 (depends on 19) The non-transitory computer readable storage medium of claim 19, further including instructions stored thereon, which when read and executed by the one or more computer processors, cause the one or more computer processors to perform steps comprising: retrieving a prior status of the cloud hardware and/or the plurality of cloud applications; and determining that the cloud hardware and/or the impacted cloud application were previously healthy before identifying the impacted cloud application and/or the impacted cloud hardware.