Abstract: This application sets forth various techniques for monitoring a status of a service. According to some embodiments, a DNS server can implement a health check engine that monitors the status of the service in order to implement round-robin DNS among a plurality of availability zones. Each service instance for the service can include a monitoring agent configured to (1) monitor the status of the service instance, and (2) respond to health check messages received from the health check engine. The monitoring agent can also be configured to (1) collect statistics associated with one or more service dependencies of the service instance during a tracking window, (2) calculate at least one ratio based on the statistics collected during the tracking window, and (3) generate the status of the service instance by comparing the at least one ratio to a threshold value.

Abstract: This application sets forth various techniques for monitoring a status of a service. According to some embodiments, a DNS server can implement a health check engine that monitors the status of the service in order to implement round-robin DNS among a plurality of availability zones. Each service instance for the service can include a monitoring agent configured to (1) monitor the status of the service instance, and (2) respond to health check messages received from the health check engine. The monitoring agent can also be configured to (1) collect statistics associated with one or more service dependencies of the service instance during a tracking window, (2) calculate at least one ratio based on the statistics collected during the tracking window, and (3) generate the status of the service instance by comparing the at least one ratio to a threshold value.

Abstract: This application sets forth various techniques for monitoring a status of a service. According to some embodiments, a DNS server can implement a health check engine that monitors the status of the service in order to implement round-robin DNS among a plurality of availability zones. Each service instance for the service can include a monitoring agent configured to (1) monitor the status of the service instance, and (2) respond to health check messages received from the health check engine. The monitoring agent can also be configured to (1) collect statistics associated with one or more service dependencies of the service instance during a tracking window, (2) calculate at least one ratio based on the statistics collected during the tracking window, and (3) generate the status of the service instance by comparing the at least one ratio to a threshold value.

Abstract: This application relates to controlling a rollout for an update to an application installed on client devices. A digital distribution platform can include at least one server connected to a network and configured to enable client devices to access resources, stored on network devices, so that applications or updates to applications can be installed on the client devices. A server can implement a service that receives a request to identify whether the update is available via a digital distribution platform and determine whether a client device is authorized to install the update. The service can be configured to sort the client device into a first subset of client devices or a second subset of client devices based on a user identifier, a version identifier, and (optionally) an application identifier. In this manner, the service can implement a gradual rollout of an update over a period of time.

Abstract: This application sets forth various techniques for monitoring a status of a service. According to some embodiments, a DNS server can implement a health check engine that monitors the status of the service in order to implement round-robin DNS among a plurality of availability zones. Each service instance for the service can include a monitoring agent configured to (1) monitor the status of the service instance, and (2) respond to health check messages received from the health check engine. The monitoring agent can also be configured to (1) collect statistics associated with one or more service dependencies of the service instance during a tracking window, (2) calculate at least one ratio based on the statistics collected during the tracking window, and (3) generate the status of the service instance by comparing the at least one ratio to a threshold value.