IP Library Granted Patent US 11,722,507
Granted Patent B1
US 11,722,507 · App. 17/698,992 · Granted Aug 8, 2023

User configurable alert notifications applicable to search query results

Inventors: Nicholas J. Filippi (Atherton, CA); Siegfried Puchbauer-Schnabel (San Francisco, CA); Carl S. Yestrau (San Francisco, CA); Vivian Shen (San Francisco, CA); J. Mathew Elting (San Francisco, CA)
Assignee: Splunk Inc.
H04L63/1425G06F9/542G06F16/21G06F16/3331G06F16/90344H04L41/0686H04L51/23H04L67/02H04L41/22H04L65/65
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 11,722,507
App. No.
17/698,992
Granted
Aug 8, 2023
Kind
B1
Abstract

The disclosed embodiments relate to a system that generates an alert based on information extracted from search results generated by a query. During operation, the system executes the query to generate the search results. The system also obtains configuration information for the alert, wherein the configuration information identifies information associated with the search results, and also specifies a trigger condition for the alert. Next, when the trigger condition for the alert is met, the system uses the configuration information to generate a payload containing the identified information associated with the search results. The system then invokes alert-generating functionality and provides the payload as input to the alert-generating functionality. This enables the alert-generating functionality to use the information from the search results while performing one or more alert actions association with the alert.

Claims (43)

1. A method, comprising:

causing display, within an alert user interface (UI), of an event included in a search result;

receiving, based at least in part on one or more inputs to the alert UI, a request to execute an alert action for the event;

determining one or more substitution token locations corresponding to the alert action;

inserting one or more values at the substitution token locations to generate a payload, the one or more values determined based at least in part on information associated with the event; and

causing execution of the alert action based at least in part on the payload.

2. The method of claim 1 , further comprising configuring the alert action using the alert UI or another UI.

3. The method of claim 1 , further comprising:

determining, based at least in part on the request, that the alert action has not been configured; and

presenting the alert UI or another UI to allow a user to configure the alert action, the configuring of the alert action including indicating the one or more substitution token locations.

4. The method of claim 1 , wherein the request to execute the alert action includes at least one of selecting the alert action from a plurality of alert actions or entering a text string representative of the alert action using the alert UI.

5. The method of claim 1 , further comprising querying a plurality of events derived from raw data to generate the search result, the plurality of events including the event.

6. The method of claim 1 , wherein the alert action includes at least one of generating an email instantiating a chat application, generating a notification, updating firewall information, or executing a user-defined alert action.

7. The method of claim 1 , wherein the information associated with the event includes an internet protocol (IP) address, and the alert action modifies a firewall rule with respect to the IP address.

8. A system comprising:

one or more processors;

one or more memory devices storing instructions thereon that, when executed by the one or more processors, cause the one or more processors to execute operations comprising:

causing display, within an alert user interface (UI), of an event included in a search result;

receiving, based at least in part on one or more inputs to the alert a request to execute an alert action for the event;

determining one or more substitution token locations corresponding to the alert action;

inserting one or more values at the substitution token locations to generate a payload, the one or more values determined based at least in part on information associated with the event; and

causing execution of the alert action based at least in part on the payload.

9. The system of claim 8 , wherein the operations further comprise configuring the alert action using the alert UI or another UI.

10. The system of claim 8 , wherein the operations further comprise:

determining, based at least in part on the request, that the alert action has not been configured; and

presenting the alert UI or another UI to allow a user to configure the alert action, the configuring of the alert action including indicating the one or more substitution token locations.

11. The system of claim 8 , wherein the request to execute the alert action includes at least one of selecting the alert action from a plurality of alert actions or entering a text string representative of the alert action using the alert UI.

12. The system of claim 8 , wherein the operations further comprise querying a plurality of events derived from raw data to generate the search result, the plurality of events including the event.

13. The system of claim 8 , wherein the alert action includes at least one of generating an email, instantiating a chat application, generating a notification, updating firewall information, or executing a user-defined alert action.

14. The system of claim 8 , wherein the information associated with the event includes an internet protocol (IP) address, and the alert action modifies a firewall rule with respect to the IP address.

15. One or more non-transitory computer-storage media storing instructions that, when executed by one or more processors, cause the one or more processors to execute operations comprising:

causing display, within an alert user interface (UI), of an event included in a search result:

receiving, based at least in part on one or more inputs to the alert UI, a request to execute an alert action for the event;

determining one or more substitution token locations corresponding to the alert action;

inserting one or more values at the substitution token locations to generate a payload, the one or more values determined based at least in part on information associated with the event; and

causing execution of the alert action based at least in part on the payload.

16. The one or more non-transitory computer-storage media of claim 15 , wherein the operations further comprise configuring the alert action using the alert UI or another UI.

17. The one or more non-transitory computer-storage media of claim 15 , wherein the operations further comprise:

determining, based at least in part on the request, that tine alert action has not been configured; and

presenting the alert UI or another UI to allow a user to configure the alert action, the configuring of the alert action including indicating the one or more substitution token locations.

18. The one or more non-transitory computer-storage media of claim 15 , wherein the request to execute the alert action includes at least one of selecting the alert action from a plurality of alert actions or entering a text string representative of the alert action using the alert UI.

19. The one or more non-transitory computer-storage media of claim 15 , wherein the operations further comprise querying a plurality of events derived from raw data to generate the search result, the plurality of events including the event.

20. The one or more non-transitory computer-storage media of claim 15 , wherein the alert action includes at least one of generating an email, instantiating a chat application, generating a notification, updating firewall information, or executing a user-defined alert action.

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 Mar 25, 2022
From: FILIPPI, NICHOLAS J.; PUCHBAUER-SCHNABEL, SIEGFRIED; YESTRAU, CARL S.; SHEN, VIVIAN; ELTING, J. MATHEW
To: SPLUNK INC.
Reel/Frame 059404/0360 →
Continuity (4)
Continuation 16944127 · Jul 30, 2020
Continuation 16177394 · Oct 31, 2018
Continuation 15499852 · Apr 27, 2017
Continuation 14698724 · Apr 28, 2015