# US 12,184,474 B2 · Action recommendations for operational issues > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,184,474 B2 - Document ID: US12184474B2 - Status: Granted - Kind: B2 - Application number: 18/534,900 - Filed: 2023-12-11 - Published: 2024-03-28 - Granted: 2024-12-31 - Earliest claimed: 2022-03-17 - Assignees: PagerDuty, Inc. - Applicants: PagerDuty, Inc. - Inventors: Vijay Shankar Venkataraman; Sanghamitra Goswami; Irena Grabovitch-Zuyev - Web page: https://patentgrep.com/patent/US12184474B2 ## CPC - H04L 41/0631: using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis - H04L 41/0654: using network fault recovery (ring fault isolation or reconfiguration in loop networks without recovery actions by a network management system H04L12/437) - H04L 41/0883: {Semiautomatic configuration, e.g. proposals from system} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## 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. ## Claims ### Claim 1 A method, comprising: identifying that an information technology (IT) component is associated with a first alert having an alert type; outputting, for user selection, first recommended actions associated with the IT component, wherein the first recommended actions include a recommended action associated with the IT component; receiving a first user input of a user-selected action; determining that the first recommended actions do not include the user-selected action; decreasing an alert-to-component likelihood between the IT component and the alert type based on the determination that the first recommended actions do not include the user-selected action; identifying that the IT component is associated with a second alert based on the alert-to-component likelihood exceeding an alert-to-component likelihood threshold; outputting, for user selection, second recommended actions associated with the IT component, wherein the second recommended actions do not include the recommended action and includes the user-selected action; receiving a second user input of the user-selected action; transmitting a request to execute the user-selected action; receiving a third user input of the user-selected action responsive to a third alert not associated with another IT component that is different from the IT component; and responsive to the third user input, associating the user-selected action with the another IT component. ### Claim 2 (depends on 1) The method of claim 1, further comprising: modifying an action-to-component likelihood between the user-selected action and the IT component based on feedback data relating to whether the user-selected action resolved the second alert. ### Claim 3 (depends on 1) The method of claim 1, further comprising: determining that the user-selected action resolved the second alert based on a determination that no additional requests to execute actions were received between a first time of receiving the user-selected action and a second time of receiving user input resolving the second alert. ### Claim 4 (depends on 1) The method of claim 1, further comprising: determining that the user-selected action resolved the second alert based on user input indicating that the user-selected action resolved the second alert. ### Claim 5 (depends on 1) The method of claim 1, wherein the second recommended actions are identified based on respective action-to-component association likelihoods between the IT component and the second recommended actions exceeding an action-to-component likelihood threshold. ### Claim 6 (depends on 1) The method of claim 1, wherein the IT component is identified using string matching on data associated with the first alert. ### Claim 7 A system, comprising: a memory; and a processor, the processor configured to execute instructions stored in the memory to: identify that an information technology (IT) component is associated with a first alert having an alert type; output, for user selection, first recommended actions associated with the IT component, wherein the first recommended actions include a recommended action associated with the IT component; receive a first user input of a user-selected action; determine that the first recommended actions do not include the user-selected action; decrease an alert-to-component likelihood between the IT component and the alert type based on the determination that the first recommended actions do not include the user-selected action; identify that the IT component is associated with a second alert based on the alert-to-component likelihood exceeding an alert-to-component likelihood threshold; output, for user selection, second recommended actions associated with the IT component, wherein the second recommended actions do not include the recommended action and includes the user-selected action; receive a second user input of the user-selected action; transmit a request to execute the user-selected action; receive a third user input of the user-selected action responsive to a third alert not associated with another IT component that is different from the IT component; and responsive to the third user input, associate the user-selected action with the another IT component. ### Claim 8 (depends on 7) The system of claim 7, wherein the processor is further configured to execute instructions stored in the memory to: modify an action-to-component likelihood between the user-selected action and the IT component based on feedback data relating to whether the user-selected action resolved the second alert. ### Claim 9 (depends on 7) The system of claim 7, wherein the processor is further configured to execute instructions stored in the memory to: determine that the user-selected action resolved the second alert based on a determination that no additional requests to execute actions were received between a first time of receiving the user-selected action and a second time of receiving user input resolving the second alert. ### Claim 10 (depends on 7) The system of claim 7, wherein the processor is further configured to execute instructions stored in the memory to: determine that the user-selected action resolved the second alert based on user input indicating that the user-selected action resolved the second alert. ### Claim 11 (depends on 7) The system of claim 7, wherein the second recommended actions are identified based on respective action-to-component association likelihoods between the IT component and the second recommended actions exceeding an action-to-component likelihood threshold. ### Claim 12 (depends on 7) The system of claim 7, wherein the IT component is identified using string matching on data associated with the first alert. ### Claim 13 A non-transitory computer readable medium storing instructions operable to cause one or more processors to perform operations comprising: identifying that an information technology (IT) component is associated with a first alert having an alert type; outputting, for user selection, first recommended actions associated with the IT component, wherein the first recommended actions include a recommended action associated with the IT component; receiving a first user input of a user-selected action; determining that the first recommended actions do not include the user-selected action; decreasing an alert-to-component likelihood between the IT component and the alert type based on the determination that the first recommended actions do not include the user-selected action; identifying that the IT component is associated with a second alert based on the alert-to-component likelihood exceeding an alert-to-component likelihood threshold; outputting, for user selection, second recommended actions associated with the IT component, wherein the second recommended actions do not include the recommended action and includes the user-selected action; receiving a second user input of the user-selected action; transmitting a request to execute the user-selected action; receiving a third user input of the user-selected action responsive to a third alert not associated with another IT component that is different from the IT component; and responsive to the third user input, associating the user-selected action with the another IT component. ### Claim 14 (depends on 13) The non-transitory computer readable medium of claim 13, wherein the operations further comprise: modifying an action-to-component likelihood between the user-selected action and the IT component based on feedback data relating to whether the user-selected action resolved the second alert. ### Claim 15 (depends on 13) The non-transitory computer readable medium of claim 13, wherein the operations further comprise: determining that the user-selected action resolved the second alert based on a determination that no additional requests to execute actions were received between a first time of receiving the user-selected action and a second time of receiving user input resolving the second alert. ### Claim 16 (depends on 13) The non-transitory computer readable medium of claim 13, wherein the operations further comprise: determining that the user-selected action resolved the second alert based on user input indicating that the user-selected action resolved the second alert. ### Claim 17 (depends on 13) The non-transitory computer readable medium of claim 13, wherein the second recommended actions are identified based on respective action-to-component association likelihoods between the IT component and the second recommended actions exceeding an action-to-component likelihood threshold.