US 10,542,071 B1Granted

Event driven health checks for non-HTTP applications

AssigneeAmazon Technologies, Inc.

InventorsNicholas Channing Matthews, Joshua Campbell

Life of this patent

Estimating the term…

Loading patent…

Abstract

Techniques are disclosed for monitoring the health of a computing application, system or service. A health monitoring service performs event driven health status checks for applications that use non-HTTP workloads. To do so, heath status messages (e.g., HTTP status requests) are directed to an API gateway at a specified frequency. In response to each health status message, the API gateway triggers at least a first event driven function to perform a health check of an application. Results of the health-status check performed by the first event driven function may be written to a status database. Further, results of the first event driven function can result in additional event driven functions being triggered (e.g., to remove an unhealthy application from production use).

Claims21

Dependent claims

A non-transitory computer-readable medium storing instructions executable to perform an operation for monitoring a health status of a computing application, the operation comprising:

receiving, at an application programming interface (API) gateway, a request comprising a Hypertext Transfer Protocol (HTTP) status request message, the request specifying to perform a non-HTTP health status check of a non-HTTP application on at least a first computing host configured to respond to HTTP health status checks, wherein the HTTP and non-HTTP health status checks evaluate HTTP and non-HTTP loads of the first computing host, respectively;
in response to the request, invoking at least a first event-driven function by operation of one or more computer processors when executing the instructions, wherein the first event-driven function receives a set of input parameters determined based at least on the HTTP status request message, wherein the first event-driven function performs the non-HTTP health status check of the non-HTTP application on the first computing host;
upon receiving a result of the non-HTTP health status check performed by the first event-driven function, writing the result to a status database that includes healthy-status and unhealthy-status tables storing indications of successful and unsuccessful status checks, respectively;
determining a healthy or unhealthy overall status of the non-HTTP application, based on evaluating one or more event-triggering conditions associated with the received result, wherein the one or more event-triggering conditions specify at least (i) a count of non-HTTP health status checks sharing the same status selected from a healthy status and an unhealthy status and (ii) a time window to which the count pertains;
and
upon determining, based on the one or more event-triggering conditions being satisfied, that the non-HTTP application has the unhealthy overall status, invoking at least a second event-driven function that includes a corrective action configured to revert the non-HTTP application to the healthy overall status, wherein the second event-driven function is configured to perform the corrective action upon successfully performing a locking mechanism on records of the unhealthy status table, in order to prevent more than one corrective action from being concurrently performed on the non-HTTP application.

3 more elements

A system to monitor a health status of a computing application, the system comprising:

one or more computer processors;
and
a memory storing instructions, which, when executed on the one or more computer processors, perform an operation comprising:
receiving, at an application programming interface (API) gateway, a request comprising a Hypertext Transfer Protocol (HTTP) status request message, the request specifying to perform a non-HTTP health status check of a non-HTTP application on at least a first computing host configured to respond to HTTP health status checks, wherein the HTTP and non-HTTP health status checks evaluate HTTP and non-HTTP loads of the first computing host, respectively;
in response to the request, invoking at least a first event-driven function, wherein the first event-driven function receives a set of input parameters determined based at least on the HTTP status request message, wherein the first event-driven function performs the non-HTTP health status check of the non-HTTP application on the first computing host;
upon receiving a result of the non-HTTP health status check performed by the first event-driven function, writing the result to a status database that includes healthy-status and unhealthy-status tables storing indications of successful and unsuccessful status checks, respectively;
determining a healthy or unhealthy overall status of the non-HTTP application, based on evaluating one or more event-triggering conditions associated with the received result, wherein the one or more event-triggering conditions specify at least (i) a count of non-HTTP health status checks sharing the same status selected from a healthy status and an unhealthy status and (ii) a time window to which the count pertains;
and
upon determining, based on the one or more event-triggering conditions being satisfied, that the non-HTTP application has the unhealthy overall status, invoking at least a second event-driven function that includes a corrective action configured to revert the non-HTTP application to the healthy overall status, wherein the second event-driven function is configured to perform the corrective action upon successfully performing a locking mechanism on records of the unhealthy status table, in order to prevent more than one corrective action from being concurrently performed on the non-HTTP application.

6 more elements

A computer-implemented method for monitoring a health status of a computing application, the computer-implemented method comprising:

receiving, at an application programming interface (API) gateway, a request comprising a Hypertext Transfer Protocol (HTTP) status request message, the request specifying to perform a non-HTTP health status check of a non-HTTP application on at least a first computing host configured to respond to HTTP health status checks, wherein the HTTP and non-HTTP health status checks evaluate HTTP and non-HTTP loads of the first computing host, respectively;
in response to the request, invoking at least a first event-driven function by operation of one or more computer processors, wherein the first event-driven function receives a set of input parameters determined based on at least the HTTP status request message, wherein the first event-driven function performs the non-HTTP health status check of the non-HTTP application on the first computing host;
upon receiving a result of the non-HTTP health status check performed by the first event-driven function, writing the result to a status database that includes healthy-status and unhealthy-status tables storing indications of successful and unsuccessful status checks, respectively;
determining a healthy or unhealthy overall status of the non-HTTP application, based on evaluating one or more event-triggering conditions associated with the received result, wherein the one or more event-triggering conditions specify at least (i) a count of non-HTTP health status checks sharing the same status selected from a healthy status and an unhealthy status and (ii) a time window to which the count pertains;
and
upon determining, based on the one or more event-triggering conditions being satisfied, that the non-HTTP application has the unhealthy overall status, invoking at least a second event-driven function that includes a corrective action configured to revert the non-HTTP application to the healthy overall status, wherein the second event-driven function is configured to perform the corrective action upon successfully performing a locking mechanism on records of the unhealthy status table, in order to prevent more than one corrective action from being concurrently performed on the non-HTTP application.

3 more elements

Dependencies are inferred from the claim text.