Aggregated health monitoring of a cluster during test automation

A method, comprising:

• initializing an interface to an application programming interface (API) server, wherein the interface is operable to send status information from two or more components within a cluster via a single output stream;
• configuring the API server, via the interface, to modify the single output stream of the API server to output status information associated with a first component of the two or more components within the cluster, wherein the single output stream sends the status information external to the cluster;
• aggregating the status information by receiving status information from the first component and a second component within the cluster, determining whether the status information from the second component affects the first component, and upon determining that the status information from the second component does affect the first component, combining the status information from the first component with the status information from the second component;
• determining, based on the aggregated status information received from the API server, whether the cluster is at a failure point;
• and
• in response to determining that the cluster is at a failure point, setting an execution signal to false, wherein the execution signal is accessible to an automation tool in communication with the cluster.

A non-transitory machine readable medium storing code, which when executed by a processor is configured to:

• initialize an interface to an application programming interface (API) server, wherein the interface is operable to send status information from two or more components within a cluster via a single output stream;
• configure the API server, via the interface, to modify the single output stream of the API server to output status information associated with a first component of the two or more components within the cluster, wherein the single output stream sends the status information external to the cluster;
• aggregate the status information by receiving status information from the first component and a second component within the cluster, determining whether the status information from the second component affects the first component, and upon determining that the status information from the second component does affect the first component, combining the status information from the first component with the status information from the second component;
• determine, based on the aggregated status information received from the API server, whether the cluster is at a failure point;
• and
• in response to determining that the cluster is at a failure point, set an execution signal to false, wherein the execution signal is accessible to an automation tool in communication with the cluster.