# US 12,118,413 B2 · Aggregated health monitoring of a cluster during test automation > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,118,413 B2 - Document ID: US12118413B2 - Status: Granted - Kind: B2 - Application number: 18/220,036 - Filed: 2023-07-10 - Published: 2023-11-16 - Granted: 2024-10-15 - Earliest claimed: 2020-11-25 - Assignees: Red Hat, Inc. - Applicants: Red Hat, Inc. - Inventors: Naga Ravi Chaitanya Elluri - Web page: https://patentgrep.com/patent/US12118413B2 ## CPC - G06F 9/547: {Remote procedure calls [RPC]; Web services} - G06F 11/3006: {where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems (multiprogramming arrangements G06F9/46; allocation of resources G06F9/50)} - G06F 9/45558: {Hypervisor-specific management and integration aspects} - G06F 11/0709: {in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems} - G06F 11/0751: {Error or fault detection not based on redundancy (power supply failures G06F1/30; network fault management H04L41/06)} - G06F 11/0769: {Readable error formats, e.g. cross-platform generic formats, human understandable formats} - G06F 11/301: {where the computing system is a virtual computing platform, e.g. logically partitioned systems (virtual machines G06F9/45533; logical partitioning of resources G06F9/5077)} - G06F 11/3055: {Monitoring arrangements for monitoring the status of the computing system or of the computing system component, e.g. monitoring if the computing system is on, off, available, not available (error or fault processing without redundancy G06F11/0703; error detection or correction by redundancy in data representation G06F11/08; error detection or correction of the data by redundancy in operations G06F11/14; error detection or correction by redundancy in hardware G06F11/16)} - G06F 11/3089: {Monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors, sensors, probes, agents (software debugging using additional hardware using a specific debug interface G06F11/3656; performance evaluation by tracing or monitoring G06F11/3466)} - G06F 2009/45591: {Monitoring or debugging support} - G06F 2009/45595: {Network integration; Enabling network access in virtual machine instances} - G06Q 10/10: Office automation; Time management - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR ## Abstract A system includes a cluster of nodes, memory, and a processor, where the cluster includes an application programming interface (API) server and one or more components. The processor is configured to initialize an interface to the API server, where the interface is operable to send status information from the one or more components within the cluster via a single output stream. The API server is configured to modify the single output stream of the API server to output status information associated with a first component of the one or more components within the cluster. The status information is aggregated and it is determined whether the cluster is at a failure point. In response to determining that the cluster is at a failure point, an execution signal is set to false, where the execution signal is accessible to an automation tool in communication with the cluster. ## Claims ### Claim 1 A system, comprising: a cluster of nodes, wherein the cluster includes an application programming interface (API) server and two or more components; a memory; and a processor in communication with the memory, wherein the processor is configured to: configure the API server, via an interface, to modify a 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 from the two or more components; 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 the failure point, set an execution signal to false, wherein the execution signal is accessible to an automation tool in communication with the cluster, and wherein upon detecting that the execution signal is set to false, the automation tool reduces an amount of stimulus sent to the cluster. ### Claim 2 (depends on 1) The system of claim 1, wherein one or more of the components includes applications executing on the cluster. ### Claim 3 (depends on 1) The system of claim 1, wherein upon detecting that the execution signal is set to false, the automation tool stops sending stimulus to the cluster. ### Claim 4 (depends on 3) The system of claim 3, wherein the stimulus includes inputs to an application executing in the cluster, wherein execution of the application affects the first component. ### Claim 5 (depends on 3) The system of claim 3, wherein the stimulus includes one or more inputs sent to one or more components within the cluster. ### Claim 6 (depends on 1) The system of claim 1, wherein the execution signal is accessible through a Hypertext Transfer Protocol interface. ### Claim 7 (depends on 1) The system of claim 1, wherein the processor is further configured to: store the status information external to the cluster. ### Claim 8 (depends on 1) The system of claim 1, wherein the automation tool is stress testing the first component. ### Claim 9 (depends on 1) The system of claim 1, wherein the processor is further configured to: in response to determining that the cluster is stable, set the execution signal to true. ### Claim 10 A method, comprising: configuring an application programming interface (API) server, via an interface, to modify a single output stream of the API server to output status information associated with a first component of two or more components within a cluster, wherein the single output stream sends the status information external to the cluster; aggregating the status information from the two or more components; 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 the failure point, setting an execution signal to false, wherein the execution signal is accessible to an automation tool in communication with the cluster, and wherein upon detecting that the execution signal is set to false, the automation tool reduces an amount of stimulus sent to the cluster. ### Claim 11 (depends on 10) The method of claim 10, wherein one or more of the components includes applications executing on the cluster. ### Claim 12 (depends on 10) The method of claim 10, wherein upon detecting that the execution signal is set to false, the automation tool modifies stimulus sent to the cluster. ### Claim 13 (depends on 12) The method of claim 12, wherein modifying the stimulus sent to the cluster includes stopping all the stimulus sent to the cluster. ### Claim 14 (depends on 12) The method of claim 12, wherein the stimulus includes one or more inputs sent to one or more components within the cluster. ### Claim 15 (depends on 10) The method of claim 10, wherein the automation tool is executing a chaos test on the cluster. ### Claim 16 (depends on 10) The method of claim 10, further comprising: in response to determining that the cluster is stable, setting the execution signal to true. ### Claim 17 A non-transitory machine readable medium storing code, which when executed by a processing device is configured to: configure an application programming interface (API) server, via an interface, to modify a single output stream of the API server to output status information associated with a first component of two or more components within a cluster, wherein the single output stream sends the status information external to the cluster; aggregate the status information from the two or more components; 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 the failure point, set an execution signal to false, wherein the execution signal is accessible to an automation tool in communication with the cluster, and wherein upon detecting that the execution signal is set to false, the automation tool reduces an amount of stimulus sent to the cluster. ### Claim 18 (depends on 17) The non-transitory machine readable medium of claim 17, wherein when the code is executed the processing device is further configured to: store the status information external to the cluster. ### Claim 19 (depends on 17) The non-transitory machine readable medium of claim 17, wherein when the code is executed the processing device is further configured to: in response to determining that the cluster is stable, set the execution signal to true.