# US 11,121,914 B2 · Monitoring and self-healing of deployed environments

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

- Number: US 11,121,914 B2
- Document ID: US11121914B2
- Status: Granted
- Kind: B2
- Application number: 16/693,139
- Filed: 2019-11-22
- Published: 2021-05-27
- Granted: 2021-09-14
- Earliest claimed: 2019-11-22
- Assignees: Walmart Apollo, LLC
- Applicants: Walmart Apollo, LLC
- Inventors: Joshua Ledbetter; Jeremy Wayne Bowman; Michael Samuhasilp; Nathan Anderson; Maria Cecilia Bustos
- Web page: https://patentgrep.com/patent/US11121914B2

## CPC

- H04L 43/0817: by checking functioning
- H04L 41/0631: using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
- H04L 41/0654: using network fault recovery (ring fault isolation or reconfiguration in loop networks without recovery actions by a network management system H04L12/437)
- H04L 41/0686: Additional information in the notification, e.g. enhancement of specific meta-data
- H04L 41/069: using logs of notifications; Post-processing of notifications
- H04L 41/0695: the faulty arrangement being the maintenance, administration or management system
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Systems and methods for monitoring and correcting a cloud environment are disclosed. An alert associated with an active issue at a component is received and an issue object is generated based on the alert. A self-healing flow is executed based on an alert type of the alert to attempt to correct the active issue.

## Claims

### Claim 1

A system for monitoring a cloud environment, comprising:
a memory having instructions stored thereon, and a processor computing device configured to read the instructions to:
receive an alert associated with an active issue of a component;
query a set of active issue objects based on the alert;
when an active issue object is not identified based on the alert:
generate an issue object based on the alert;
identify the alert as a first alert of the issue object; and
execute a self-healing flow based on an alert type of the alert; and
when an active issue object is identified based on the alert:
identify the alert as a subsequent alert of the active issue object; and
execute a self-healing flow based on the alert type of the alert and an alert type of a first alert of the active issue object.

### Claim 2 (depends on 1)

The system of claim 1, wherein executing the self-healing flow comprises:
obtaining a self-healing object based on the alert type of the first alert of the issue object or the subsequent alert of the active issue object, wherein the self-healing object is updated based on the first alert of the issue object or the subsequent alert of the active issue object;
obtaining a self-healing flow from a self-healing flow collection; and
executing the self-healing flow.

### Claim 3 (depends on 2)

The system of claim 2, wherein executing the self-healing flow comprises verifying that the self-healing flow corrected the active issue associated with the alert and identifying the self-healing object as closed.

### Claim 4 (depends on 1)

The system of claim 1, wherein the computing device is configured to generate a first platform-specific alert for a first platform.

### Claim 5 (depends on 4)

The system of claim 4, wherein the first platform is selected based on the alert type of the alert.

### Claim 6 (depends on 4)

The system of claim 4, wherein the computing system is configured to generate a second platform-specific alert for a second platform.

### Claim 7 (depends on 1)

The system of claim 1, wherein the alert includes a predetermined package.

### Claim 8 (depends on 1)

The system of claim 1, wherein the computing device is configured to:
receive a subsequent alert generated by the component for the active issue; and
update the issue object based on the subsequent alert.

### Claim 9

A non-transitory computer readable medium having instructions stored thereon, wherein the instructions, when executed by a processor cause a device to perform operations comprising:
receiving an alert associated with an active issue of a component;
querying a set of active issue objects based on the alert;
when an active issue object is not identified based on the alert:
generating an issue object based on the alert;
identifying the alert as a first alert of the issue object; and
executing a self-healing flow based on an alert type of the alert; and
when an active issue object is identified based on the alert:
identifying the alert as a subsequent alert of the active issue object; and
executing a self-healing flow based on the alert type of the alert and an alert type of a first alert of the active issue object.

### Claim 10 (depends on 9)

The non-transitory computer readable medium of claim 9, wherein the instructions for executing the self-healing flow comprise instructions that cause the device to perform operations comprising:
creating a self-healing document based on the alert type;
loading a self-healing flow from a self-healing flow collection; and
executing the self-healing flow.

### Claim 11 (depends on 10)

The non-transitory computer readable medium of claim 10, wherein the instructions for executing the self-healing flow comprise instructions that cause the device to perform operations comprising verifying that the self-healing flow corrected the active issue associated with the alert.

### Claim 12 (depends on 9)

The non-transitory computer readable medium of claim 9, wherein the instructions cause the device to perform operations comprising generating a first platform-specific alert for a first platform.

### Claim 13 (depends on 12)

The non-transitory computer readable medium of claim 12, wherein the first platform is selected based on the alert type of the alert.

### Claim 14 (depends on 12)

The non-transitory computer readable medium of claim 12, wherein the computing system is configured to generate a second platform-specific alert for a second platform.

### Claim 15 (depends on 9)

The non-transitory computer readable medium of claim 9, wherein the alert includes a predetermined package.

### Claim 16 (depends on 9)

The non-transitory computer readable medium of claim 9, wherein the instructions cause the device to perform operations comprising:
receiving a subsequent alert generated by the component for the active issue; and
updating the issue object based on the subsequent alert.

### Claim 17

A computer-implemented method, comprising:
receiving an alert associated with an active issue of a component;
querying a set of active issue objects based on the alert;
when an active issue object is not identified based on the alert:
generating an issue object based on the alert;
identifying the alert as a first alert of the issue object; and
executing a self-healing flow based on an alert type of the alert; and
when an active issue object is identified based on the alert:
identifying the alert as a subsequent alert of the active issue object; and
executing a self-healing flow based on the alert type of the alert and an alert type of a first alert of the active issue object.

### Claim 18 (depends on 17)

The computer-implemented method of claim 17, wherein executing a self-healing flow comprises:
creating a self-healing document based on the alert type;
loading a self-healing flow from a self-healing flow collection; and
executing the self-healing flow.

### Claim 19 (depends on 17)

The computer-implemented method of claim 17, comprising generating a first platform-specific alert for a first platform.

### Claim 20 (depends on 17)

The computer-implemented method of claim 17, comprising:
receiving a subsequent alert generated by the component for the active issue; and
updating the issue object based on the subsequent alert.