Systems and methods to identify production incidents and provide automated preventive and corrective measures

A system for identifying production incidents and implementing automated preventive and corrective measures, the system comprising:

• a database that stores applications and host details;
• and
• a processor operatively coupled to the database via a communication network, wherein the processor is configured to:
• generate an event corresponding to a job failure or service degradation;
• generate, by the event, an incident in an automation queue;
• automatically trigger, in response to the generated incident, a self-healing service that includes:
• identifying an application to which the event generated belongs to by accessing the database;
• fetching functional identification (ID) of the application from the database, wherein the functional ID allows access to production servers to perform required mitigation steps;
• identifying a type of job failure or a service degradation;
• automatically executing, by utilizing predefined services, the steps required for mitigation;
• recording, in response to executing, outcome of the mitigation in the database along with output at each stage of execution;
• and
• evaluating the outcome of the mitigation by executing health checks to determine whether failed job or a process or a host is healthy;
• and
• close the incident based on determining that the failed job or the process or the host is healthy.

A non-transitory computer readable medium configured to store instructions for identifying production incidents and implementing automated preventive and corrective measures, wherein, when executed, the instructions cause a processor to perform the following:

• generating an event corresponding to a job failure or service degradation;
• generating, by the event, an incident in an automation queue;
• automatically triggering, in response to the generated incident, a self-healing service that includes:
• identifying an application to which the event generated belongs to by accessing a database that stores the application and host details;
• fetching functional identification (ID) of the application from the database, wherein the functional ID allows access to production servers to perform required mitigation steps;
• identifying a type of job failure or a service degradation;
• automatically executing, by utilizing predefined services, the steps required for mitigation;
• recording, in response to executing, outcome of the mitigation in the database along with output at each stage of execution;
• and
• evaluating the outcome of the mitigation by executing health checks to determine whether a failed job or a process or a host is healthy;
• and
• closing the incident based on determining that the failed job or the process or the host is healthy.