System and method for monitoring network processing optimization

A computer program product for monitoring network processing using node analysis in a communication network, in real time, wherein the computer program product is structured for precluding outages of network components from causing a system to be taken offline, based on structuring network nodes into clusters and analyzing node commands and node operations, the computer program product comprising at least one non-transitory computer-readable medium having computer-readable program code portions embodied therein, the computer-readable program code portions comprising executable portions configured to:

• receive, via at least one data collector agent component, the node operation information relating to a node command from one or more nodes of a plurality of network nodes, wherein the one or more nodes are grouped into a cluster in which a required number of nodes must be online at a given time, wherein each of the plurality of network nodes is associated with an individual server of the communication network and is connected to the data collector agent component, wherein the node command comprises server boot, server reboot, remote execution, and defined application operations;
• deny execution of the node command until approval of the node command by an application protection engine component operatively connected to the data collector agent component, wherein the application protection engine component is structured to receive (i) live input feeds and (ii) application alerts from the data collector agent component, and analyze and approve node commands associated with the plurality of network nodes;
• transmit, via the at least one data collector agent component, the node command to the application protection engine component;
• based on the node operation information, determine one or more node characteristics, wherein the node characteristics relate to one or more operating indicators and health indicators of the given node, wherein the health indicators of the given node are continuously monitored;
• compare the one or more node characteristics of the node command to one or more expected node characteristics, wherein the expected node characteristics are extracted from an application protection engine data repository and are based on the same or similar node commands previously executed, comprising determining a failing node in response to determining a deviation from the previously executed node commands;
• determine a node outage likelihood based on comparing the one or more node characteristics of the node command to one or more expected node characteristics, wherein the node outage likelihood indicates likelihood the given node will experience a node outage within a predetermined amount of time and a duration of the node outage for which the given node will be inoperable;
• determine a cluster node operation plan, wherein the cluster node operation plan is configured to determine the nodes of the cluster that must be in operation in an event of the node outage of the given node, wherein determining the cluster node operation plan further comprises:
• detecting planned node outages associated with the one or mode nodes;
• and
• modifying, in response to the node outage likelihood, the planned node outages associated with the one or mode nodes, such that the inoperability of the cluster is precluded;
• transmit a notification of the node outage likelihood indicating a replace or repair requirement for the given node;
• and
• implement an expected node outage solution for the event of the node outage of the given node.

A computer-implemented method for monitoring network processing using node analysis in a communication network, in real time, wherein the method is structured for precluding outages of network components from causing a system to be taken offline, based on structuring network nodes into clusters and analyzing node commands and node operations, the method comprising:

• receiving, via at least one data collector agent component, the node operation information relating to a node command from one or more nodes of a plurality of network nodes, wherein the one or more nodes are grouped into a cluster in which a required number of nodes must be online at a given time, wherein each of the plurality of network nodes is associated with an individual server of the communication network and is connected to the data collector agent component, wherein the node command comprises server boot, server reboot, remote execution, and defined application operations;
• denying execution of the node command until approval of the node command by an application protection engine component operatively connected to the data collector agent component, wherein the application protection engine component is structured to receive (i) live input feeds and (ii) application alerts from the data collector agent component, and analyze and approve node commands associated with the plurality of network nodes;
• transmitting, via the at least one data collector agent component, the node command to the application protection engine component;
• based on the node operation information, determining one or more node characteristics, wherein the node characteristics relate to one or more operating indicators and health indicators of the given node, wherein the health indicators of the given node are continuously monitored;
• comparing the one or more node characteristics of the node command to one or more expected node characteristics, wherein the expected node characteristics are extracted from an application protection engine data repository and are based on the same or similar node commands previously executed, comprising determining a failing node in response to determining a deviation from the previously executed node commands;
• based on the comparison of the one or more node characteristics of the node command to one or more expected node characteristics, determining a node outage likelihood, wherein the node outage likelihood indicates likelihood the given node will experience a node outage within a predetermined amount of time and a duration of the node outage for which the given node will be inoperable;
• determining a cluster node operation plan, wherein the cluster node operation plan is configured to determine the nodes of the cluster that must be in operation in an event of the node outage of the given node, wherein determining the cluster node operation plan further comprises:
• detecting planned node outages associated with the one or mode nodes;
• and
• modifying, in response to the node outage likelihood, the planned node outages associated with the one or mode nodes, such that the inoperability of the cluster is precluded;
• transmitting a notification of the node outage likelihood indicating a replace or repair requirement for the given node;
• and
• implementing an expected node outage solution for the event of the node outage of the given node.