Abstract: An information technology (IT) component associated with a first alert having an alert type is identified. A first list of recommended actions associated with the IT component is output. The first list includes a recommended action. A first user input of a user-selected action is received. An alert-to-component likelihood between the IT component and the alert type is decreased based on a determination that the first list does not include the user-selected action. The IT component is identified as being associated with a second alert based on the alert-to-component likelihood exceeding an alert-to-component likelihood threshold. A second list of recommended actions associated with the IT component is output. The second list does not include the recommended action and includes the user-selected action. A second user input of the user-selected action is received. A request to execute the user-selected action is transmitted.

Abstract: An incident that requires a resolution responsive to an event detected in a managed information technology environment is triggered. An incident type is obtained for the incident, where the incident type is selected from a set that includes a rare type, a novel type, and a frequent type. Responsive to determining that the incident is of the rare type or the frequent type, a list of recommended responders to address the incident is generated using a machine-learning model. Responsive to determining that the incident is of the novel type, a list of recommended responders to address the incident is generated based on a seniority level of responders. A selection of one of the recommended responders is received. The one of the recommended responders is associated with the incident.

Abstract: An information technology (IT) component associated with a first alert having an alert type is identified. A first list of recommended actions associated with the IT component is output. The first list includes a recommended action. A first user input of a user-selected action is received. An alert-to-component likelihood between the IT component and the alert type is decreased based on a determination that the first list does not include the user-selected action. The IT component is identified as being associated with a second alert based on the alert-to-component likelihood exceeding an alert-to-component likelihood threshold. A second list of recommended actions associated with the IT component is output. The second list does not include the recommended action and includes the user-selected action. A second user input of the user-selected action is received. A request to execute the user-selected action is transmitted.

Abstract: An information technology (IT) component associated with a first alert having an alert type is identified. A first list of recommended actions associated with the IT component is output. The first list includes a recommended action. A first user input of a user-selected action is received. An alert-to-component likelihood between the IT component and the alert type is decreased based on a determination that the first list does not include the user-selected action. The IT component is identified as being associated with a second alert based on the alert-to-component likelihood exceeding an alert-to-component likelihood threshold. A second list of recommended actions associated with the IT component is output. The second list does not include the recommended action and includes the user-selected action. A second user input of the user-selected action is received. A request to execute the user-selected action is transmitted.