System and method for fault identification, logging, and remediation

1. A client recovery orchestrator for recovering clients after faults, comprising:

a persistent storage for storing a fault correction script; and

a recovery manager programmed to:

obtain logs associated with components of a client of the clients,

generating a fault profile for a fault of the faults using the logs, wherein the fault profile is based on component dependencies of the client, wherein the component dependencies specify:

a hardware component associated with a second hardware component that generated the fault, and

a software component associated with the second hardware component that generated the fault,

match the fault profile to a corrective action based on an associative model that associates dimensions of the fault profile and the corrective action,

obtain the fault correction script based on the corrective action,

orchestrate execution of the fault correction script to obtain an updated client, and

update the associative model based on the updated client.

2. The client recovery orchestrator of claim 1 , wherein the recovery manager is further programmed to:

make a determination that the fault is still present in the client after orchestrating execution of the fault correction script;

in response to the determination:

obtain a second fault profile associated with the client.

3. The client recovery orchestrator of claim 1 , wherein the hardware component is part of the client.

4. The client recovery orchestrator of claim 1 , wherein the hardware component is not part of the client.

5. The client recovery orchestrator of claim 1 , wherein the hardware component is a portion of a solution architecture of which the client is a portion.

6. A method for recovering clients after faults, comprising:

obtaining logs associated with components of a client of the clients:

generating a fault profile for a fault of the faults using the logs, wherein the fault profile is based on component dependencies of the client, wherein the component dependencies specify:

a hardware component associated with a second hardware component that generated the fault, and

a software component associated with the second hardware component that generated the fault;

matching the fault profile to a corrective action based on an associative model that associates dimensions of the fault profile and the corrective action;

obtaining a fault correction script based on the corrective action;

executing the fault correction script to obtain an updated client; and

updating the associative model based on the updated client.

7. The method of claim 6 , further comprising:

making a determination that the fault is still present in the client after orchestrating execution of the fault correction script;

in response to the determination:

obtaining a second fault profile associated with the client.

8. The method of claim 6 , wherein the hardware component is part of the client.

9. The method of claim 6 , wherein the hardware component is not part of the client.

10. The method of claim 6 , wherein the hardware component is a portion of a solution architecture of which the client is a portion.

11. A non-transitory computer readable medium comprising computer readable program code, which when executed by a computer processor enables the computer processor to perform a method for recovering clients after faults, comprising:

obtaining logs associated with components of a client of the clients;

generating a fault profile for a fault of the faults using the logs, wherein the fault profile is based on component dependencies of the client, wherein the component dependencies specify:

a hardware component associated with a second hardware component that generated the fault, and

a software component associated with the second hardware component that generated the fault;

matching the fault profile to a corrective action based on an associative model that associates dimensions of the fault profile and the corrective action;

obtaining a fault correction script based on the corrective action;

executing the fault correction script to obtain an updated client; and

updating the associative model based on the updated client.

12. The non-transitory computer readable medium of claim 11 , wherein the method further comprises:

making a determination that the fault is still present in the client after orchestrating execution of the fault correction script;

in response to the determination:

obtaining a second fault profile associated with the client.

13. The non-transitory computer readable medium of claim 11 , wherein the hardware component is part of the client.

14. The non-transitory computer readable medium of claim 11 , wherein the hardware component is not part of the client.

15. The client recovery orchestrator of claim 1 , wherein the fault prevents the client from providing a computer implemented service.

16. The client recovery orchestrator of claim 1 , wherein the associative model relates fault profiles to corrective actions.

17. The method of claim 6 , wherein the fault prevents the client from providing a computer implemented service.

18. The method of claim 6 , wherein the associative model relates fault profiles to corrective actions.

19. The non-transitory computer readable medium of claim 11 , wherein the fault prevents the client from providing a computer implemented service.

20. The non-transitory computer readable medium of claim 11 , wherein the associative model relates fault profiles to corrective actions.