IP Library Granted Patent US 10,868,711
Granted Patent B2
US 10,868,711 · App. 16/049,730 · Granted Dec 15, 2020

Actionable alert messaging network for automated incident resolution

Inventor: Jesse Chor (Los Gatos, CA)
Assignee: Splunk Inc.
H04L41/0686G06F11/0793H04L41/14H04L43/08H04L63/1408G06F9/453G06F11/3082G06Q10/0631
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,868,711
App. No.
16/049,730
Granted
Dec 15, 2020
Kind
B2
Abstract

Machine data reflecting operation of a monitored system is ingested and made available for search by a data intake and query system (DIQS). A monitoring function may search the data ingested by the DIQS to determine instances of notable events in regards to the monitored system and may further determine a defined invokable action message (IAM) associated with a notable event instance. Processing ensues to send an IAM to a communications device used by support personnel. The IAM includes information about an action invocation message (AIM) suitable to cause the performance of an action that possibly remedies or improves an operational condition represented by the notable event. Support personnel engages a user interface representation corresponding to the AIM and the AIM is sent to a remedial node where performance of the action is invoked.

Claims (52)

1. A method comprising:

determining a notable event in respect of a monitored system at a monitor node based at least in part on information of a notable event definition, the notable event having a notable event type;

generating an invokable action message (IAM) in response to said determined notable event, the IAM including information based at least in part on an IAM definition associated with the notable event type, the IAM definition having user-configured information comprising IAM information and action invocation message (AIM) information;

sending the IAM to a support communications device (SCD) identified at least in part by destination information of the IAM definition;

receiving the IAM at the SCD;

causing the presentation of a user interface having an interactive element enabling a user to indicate an invokable action identified in the invokable action message in response to the received IAM;

receiving input at the support communications device indicating user interaction with the interactive element; and

sending an action invocation message (AIM) from the support communications device to a remedial action node in response to the received input, the AIM based at least in part on information of the IAM to thereby cause the performance of the invokable action.

2. The method of claim 1 wherein receiving the IAM comprises receiving the generated IAM or receiving an automatically produced derivative of the generated IAM.

3. The method of claim 1 wherein receiving the IAM comprises receiving the IAM via a cellular communications network.

4. The method of claim 1 wherein the destination information of the IAM definition comprises a telephone number.

5. The method of claim 1 wherein the user-configured IAM information of the IAM definition comprises a title and a description.

6. The method of claim 1 wherein the user-configured IAM information of the IAM definition comprises at least one from among an identification of static context information and an identification of dynamic context information.

7. The method of claim 1 wherein the user-configured AIM information of the IAM definition comprises information identifying the remedial action node.

8. The method of claim 1 wherein the user-configured AIM information of the IAM definition comprises information identifying a network location of the remedial action node.

9. The method of claim 1 wherein the user-configured AIM information of the IAM definition comprises a Uniform Resource Identifier (URI) referencing the remedial action node.

10. The method of claim 1 wherein the user-configured AIM information of the IAM definition comprises a Uniform Resource Identifier (URI) referencing the remedial action node and the invokable action.

11. The method of claim 1 wherein the user-configured AIM information of the IAM definition comprises a Uniform Resource Locator (URL) referencing the remedial action node.

12. The method of claim 1 wherein the user-configured AIM information of the IAM definition comprises a Uniform Resource Locator (URL) referencing the remedial action node and having information to reference the invokable action included in at least one from among a URL query component and a URL fragment component.

13. The method of claim 1 wherein the user-configured AIM information of the IAM definition comprises information identifying the invokable action.

14. The method of claim 1 wherein the SCD is a handheld mobile device.

15. The method of claim 1 wherein the SCD comprises an installed application configured as the deep linking handler for at least a portion of network traffic received from the monitor node, the installed application adapted to performing said presentation of a user interface.

16. The method of claim 1 wherein the remedial action node is external to a monitoring system comprising the monitor node.

17. The method of claim 1 wherein the monitored system comprises the remedial action node.

18. The method of claim 1 wherein determining the notable event includes executing a search query based at least in part on information of the notable event definition.

19. The method of claim 1 wherein determining the notable event includes executing a search query based at least in part on information of the notable event definition, the search query being performed against data of a data intake and query system.

20. The method of claim 1 wherein determining the notable event includes executing a search query based at least in part on information of the notable event definition, the search query being performed against data of a data intake and query system (DIQS), the data of the DIQS comprising machine data and/or data derived from machine data.

21. The method of claim 1 wherein determining the notable event includes executing a search query based at least in part on information of the notable event definition, the search query being performed against data of a data intake and query system (DIQS), the data of the DIQS comprising machine data and/or data derived from machine data, the machine data comprising at least one from among event data and metrics data.

22. The method of claim 1 wherein determining the notable event includes executing a search query based at least in part on information of the notable event definition, the search query being performed against data of a data intake and query system (DIQS), the data of the DIQS comprising machine data and/or data derived from machine data, wherein the machine data is ingested from multiple sources by the DIQS and reflects the operation of the monitored system.

23. The method of claim 1 wherein determining the notable event includes executing a search query based at least in part on information of the notable event definition, the search query being performed against data of a data intake and query system (DIQS), the data of the DIQS comprising machine data and/or data derived from machine data, wherein the machine data is ingested from multiple sources by the DIQS and reflects the operation of the monitored information technology (IT) environment.

24. The method of claim 1 wherein determining the notable event includes executing a search query based at least in part on information of the notable event definition, the search query being performed against data of a data intake and query system (DIQS), the data of the DIQS comprising machine data and/or data derived from machine data, wherein the machine data is ingested from multiple sources by the DIQS and reflects the operation of the monitored information technology (IT) environment, and the machine data comprising event data.

25. The method of claim 1 wherein determining the notable event includes executing a search query based at least in part on information of the notable event definition, the search query being performed against data of a data intake and query system (DIQS), the data of the DIQS comprising machine data and/or data derived from machine data, wherein the machine data is ingested from multiple sources by the DIQS and reflects the operation of the monitored information technology (IT) environment, and the machine data comprising at least one from among event data and metrics data.

26. The method of claim 1 wherein determining the notable event includes executing a search query based at least in part on information of the notable event definition, the search query being performed against data of a data intake and query system (DIQS), the data of the DIQS comprising machine data and/or data derived from machine data, wherein the machine data is ingested from multiple sources by the DIQS and reflects the operation of the monitored information technology (IT) environment, and the machine data comprising event data and metrics data.

27. A system comprising:

a monitor node having at least one processor and memory configured to perform operations including:

determining a notable event in respect of a monitored system based at least in part on information of a notable event definition, the notable event having a notable event type;

generating an invokable action message (IAM) in response to said determined notable event, the IAM including information based at least in part on an IAM definition associated with the notable event type, the IAM definition having user-configured information comprising IAM information and action invocation message (AIM) information;

sending the IAM to a destination identified at least in part by destination information of the IAM definition; and

a support communications device coupled by a communications path to the monitor node and having at least one processor and memory configured to perform operations including:

receiving the IAM sent by the monitor node;

causing the presentation of a user interface having an interactive element enabling a user to indicate an invokable action identified in the invokable action message in response to the received IAM;

receiving input at the support communications device indicating user interaction with the interactive element; and

sending an action invocation message (AIM) from the support communications device to a remedial action node in response to the received input, the AIM based at least in part on information of the IAM to thereby cause the performance of the invokable action.

28. The system of claim 27 wherein determining the notable event includes executing a search query based at least in part on information of the notable event definition, the search query being performed against data of a data intake and query system (DIQS), the data of the DIQS comprising machine data and/or data derived from machine data, wherein the machine data is ingested from multiple sources by the DIQS and reflects the operation of the monitored information technology (IT) environment.

29. A non-transitory computer readable storage medium encoding instructions thereon that, in response to execution by one or more processing devices, cause the one or more processing devices to perform operations comprising:

determining a notable event in respect of a monitored system based at least in part on information of a notable event definition, the notable event having a notable event type;

generating an invokable action message (IAM) in response to said determined notable event, the IAM including information based at least in part on an IAM definition associated with the notable event type, the IAM definition having user-configured information comprising IAM information and action invocation message (AIM) information; and

sending the IAM to a support communications device (SCD) identified at least in part by destination information of the IAM definition, to thereby incite processing at the SCD receiving the IAM to perform operations comprising:

causing the presentation of a user interface having an interactive element enabling a user to indicate an invokable action identified in the invokable action message;

receiving input at the support communications device indicating user interaction with the interactive element; and

sending an action invocation message (AIM) from the support communications device to a remedial action node in response to the received input, the AIM based at least in part on information of the IAM to thereby cause the performance of the invokable action.

30. The non-transitory computer readable storage medium of claim 29 wherein said operation for determining the notable event includes executing a search query based at least in part on information of the notable event definition, the search query being performed against data of a data intake and query system (DIQS), the data of the DIQS comprising machine data and/or data derived from machine data, wherein the machine data is ingested from multiple sources by the DIQS and reflects the operation of the monitored information technology (IT) environment.

Assignments (4)
CHANGE OF NAME Recorded Jul 22, 2025
From: SPLUNK INC.
To: SPLUNK LLC
Reel/Frame 072170/0599 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 22, 2025
From: SPLUNK LLC
To: CISCO TECHNOLOGY, INC.
Reel/Frame 072173/0058 →
CHANGE OF NAME Recorded Jan 6, 2025
From: SPLUNK INC.
To: SPLUNK LLC
Reel/Frame 069825/0782 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 30, 2018
From: CHOR, JESSE
To: SPLUNK INC.
Reel/Frame 046505/0946 →
Continuity (2)
Provisional Application 62664921 · Apr 30, 2018
Related Publication 20190334764A1 · Oct 31, 2019
Cited By (7)
US 12,242,368 US 12,248,941 US 12,255,860 US 12,379,903 US 12,626,263 US 12,639,049 US 12,664,557