Automatic root cause analysis and prediction for a large dynamic process execution system

A method executed by a computing device for automatically determining a root cause of a failure associated with a capacity provisioning process, wherein the capacity provisioning process is for a cloud-computing system, the method comprising:

• receiving a ticket, the ticket indicating the failure;
• identifying zero or more potential root causes of the failure, wherein the zero or more potential root causes are described in root-cause records associated with one or more historical tickets;
• assigning scores to the zero or more potential root causes of the failure;
• determining whether the zero or more potential root causes include the root cause based on the scores;
• determining, if the zero or more potential root causes do not include the root cause of the failure, whether the root cause of the failure can be generated without human intervention;
• determining whether repairs for the failure are known based on the root-cause records associated with the one or more historical tickets;
• seeking human intervention if either the root cause or the repairs are unknown;
• attaching, if the root cause is known, the root cause to the ticket;
• and
• identifying, if the repairs are known, one or more repair teams to complete the repairs.

A computer-readable medium comprising instructions that are executable by one or more processors to cause a computing system to:

• receive events emitted by tasks associated with a capacity provisioning process for a cloud-computing system, wherein the events describe a status of the tasks;
• receive health signals from one or more external systems, wherein the health signals indicate whether the one or more external systems are operational;
• receive a ticket, wherein the ticket identifies a failure associated with the capacity provisioning process;
• access a data store storing historical tickets of the cloud-computing system, wherein one or more of the historical tickets have associated root-cause records;
• determine a root cause of the failure based on the events, the health signals, the historical tickets, and the associated root-cause records, wherein determining the root cause of the failure comprises pattern-matching the ticket against the historical tickets;
• determine necessary repairs for the failure based on the associated root-cause records;
• and
• determine an estimated time for the necessary repairs to be complete.