Abstract: A system implements techniques for using traffic volume associated with a service in order to proactively manage the capacity of a resource that supports the service. More specifically, the traffic volume is used as an indicator to determine, or project, a change in capacity that may be needed to avoid the under-provisioning of the resource. Alternatively, the traffic volume is used as an indicator to determine, or project, a change in capacity that may be preferred by a tenant that operates the service to avoid the over-provisioning of the resource.

Abstract: A system implements techniques for efficiently determining that an update deployed by a foundational service has caused a regression based on an aggregate health determination associated with tenant services and/or cloud resource provider services that depend upon the foundational service. The deployment of the update is initiated by an entity (e.g., an engineering team) tasked with operating and/or managing the foundational service. Accordingly, the system described herein can generate and provide a communication, to the foundational service (e.g., entity), indicating that a regression has likely been caused by the update and/or instructing the foundational service to halt the deployment of the update.

Abstract: Example aspects include techniques for employing cross-service diagnostics for cloud service providers. These techniques may include dynamically generating a workflow of one or more diagnostic modules based on relationship information between an origin service experiencing an incident and one or more related services that the origin service depends on, and executing the workflow of one or more diagnostic modules to determine a root cause of the incident, each of the one or more diagnostic modules implemented by an individual service of the one or more related services in accordance with a schema. In addition, the techniques may include determining a diagnostic action based on the root cause, and transmitting, based on the diagnostic action, an engagement notification to a responsible entity.

Abstract: Example aspects include techniques for employing cross-service diagnostics for cloud service providers. These techniques may include dynamically generating a workflow of one or more diagnostic modules based on relationship information between an origin service experiencing an incident and one or more related services that the origin service depends on, and executing the workflow of one or more diagnostic modules to determine a root cause of the incident, each of the one or more diagnostic modules implemented by an individual service of the one or more related services in accordance with a schema. In addition, the techniques may include determining a diagnostic action based on the root cause, and transmitting, based on the diagnostic action, an engagement notification to a responsible entity.

Abstract: Example aspects include techniques for employing cross-service diagnostics for cloud service providers. These techniques may include dynamically generating a workflow of one or more diagnostic modules based on relationship information between an origin service experiencing an incident and one or more related services that the origin service depends on, and executing the workflow of one or more diagnostic modules to determine a root cause of the incident, each of the one or more diagnostic modules implemented by an individual service of the one or more related services in accordance with a schema. In addition, the techniques may include determining a diagnostic action based on the root cause, and transmitting, based on the diagnostic action, an engagement notification to a responsible entity.

Abstract: Example aspects include techniques for employing cross-service diagnostics for cloud service providers. These techniques may include dynamically generating a workflow of one or more diagnostic modules based on relationship information between an origin service experiencing an incident and one or more related services that the origin service depends on, and executing the workflow of one or more diagnostic modules to determine a root cause of the incident, each of the one or more diagnostic modules implemented by an individual service of the one or more related services in accordance with a schema. In addition, the techniques may include determining a diagnostic action based on the root cause, and transmitting, based on the diagnostic action, an engagement notification to a responsible entity.