System and method for detecting and remedying faulty failover of edge network computing devices based on monitored sensor data

A method comprising:

• receiving, from a computing node, a fault event message, wherein the fault event message comprises a fault event identifier and one or more computing node parameters, wherein the fault event identifier is associated with an anomalous operation performed by the computing node;
• determining whether the received fault event identifier is a known fault event identifier based at least in part upon determining if the received fault event identifier is included in a list of known fault event identifiers stored in a historical events dataset;
• in response to determining that the received fault event identifier is not a known fault event identifier, identifying, by an AI algorithm, a first set of procedures based at least in part on a data value associated with the one or more computing node parameters not exceeding a predefined threshold value, wherein the first set of procedures includes a first potential faulty operation and a corresponding first potential remedy action, and a second potential faulty operation and a corresponding second potential remedy action, wherein the AI algorithm is trained based on a rules dataset that includes one or more rules to identify the first set of procedures to fix the anomalous operation associated with a computing node, wherein one of the rules defines identifying the first set of procedures when the data value associated with the one or more computing node parameters does not exceed a predefined threshold value;
• identifying a sequential order of execution of the identified first potential remedy action and the second potential remedy action based on at least one of a plurality of execution criteria stored in the historical events dataset, wherein the one of the plurality of execution criteria includes past number of successful fix data associated each of the first potential remedy action and the second potential remedy action, wherein the identified sequential order first executes the first potential remedy action, followed by the second potential remedy action;
• sequentially executing, on the computing node, the first potential remedy action;
• determining whether the executed first potential remedy action fixes the anomalous operation associated with the computing node;
• in response to determining that the executed first potential remedy action does not fix the anomalous operation associated with the computing node, sequentially executing, on the computing node, the second potential remedy action;
• determining whether the executed second potential remedy action fixes the anomalous operation associated with the computing node;
• in response to determining that the executed second potential remedy action does fix the anomalous operation associated with the computing node, transmitting a successful fix notification to the computing node;
• and
• inputting the received fault event identifier, the identified second potential faulty operation, and the corresponding second potential remedy action in the historical events dataset to update the historical events dataset.

A non-transitory computer-readable medium storing instructions that, when executed by a processor, cause the processor to:

• receive, from a computing node, a fault event message, wherein the fault event message comprises a fault event identifier and one or more computing node parameters, wherein the fault event identifier is associated with an anomalous operation performed by the computing node;
• determine whether the received fault event identifier is a known fault event identifier based at least in part upon determining if the received fault event identifier is included in a list of known fault event identifiers stored in a historical events dataset;
• in response to determining that the received fault event identifier is not a known fault event identifier, identify, by an AI algorithm, a first set of procedures based at least in part on a data value associated with the one or more computing node parameters not exceeding a predefined threshold value, wherein the first set of procedures includes a first potential faulty operation and a corresponding first potential remedy action, and a second potential faulty operation and a corresponding second potential remedy action, wherein the AI algorithm is trained based on a rules dataset that includes one or more rules to identify the first set of procedures to fix the anomalous operation associated with a computing node, wherein one of the rules defines identifying the first set of procedures when the data value associated with the one or more computing node parameters does not exceed a predefined threshold value;
• identify a sequential order of execution of the identified first potential remedy action and the second potential remedy action based on at least one of a plurality of execution criteria stored in the historical events dataset, wherein the one of the plurality of execution criteria includes past number of successful fix data associated each of the first potential remedy action and the second potential remedy action, wherein the identified sequential order first executes the first potential remedy action, followed by the second potential remedy action;
• sequentially execute, on the computing node, the first potential remedy action;
• determine whether the executed first potential remedy action fixes the anomalous operation associated with the computing node;
• in response to determining that the executed first potential remedy action does not fix the anomalous operation associated with the computing node, sequentially execute, on the computing node, the second potential remedy action;
• determine whether the executed second potential remedy action fixes the anomalous operation associated with the computing node;
• in response to determining that the executed second potential remedy action does fix the anomalous operation associated with the computing node, transmit a successful fix notification to the computing node;
• and
• input the received fault event identifier, the identified second potential faulty operation, and the corresponding second potential remedy action in the historical events dataset to update the historical events dataset.