Is there a way to aggregate multiple notable events created by a single correlation search?

[sspinner]

If I create a correlation search that returns multiple results, each result creates a separate notable event. However, in some cases, we only want a single notable event to be created containing the aggregated results. Is there a method for doing this?

Note, alerting based on a correlation search that returns multiple events seems to aggregate by default. The option doesn’t appear explicitly in the Correlation Search edit page, but the option “Alert mode: once per search” in the non-ES saved search page associated with the correlation search is set (and I don't remember doing anything to enable that).

Alternatively, given that the alerting is aggregated, it actually makes sense that the events appear individually in the notable events index. The real problem is in the Incident Review dashboard. Is there a way in the dashboard to aggregate events by instance of the calling correlation search as is done for the alerts?

[jcoates_splunk]

Hi,

question 1, it's easiest to set up your search so that it triggers for the fact of correlation, not the bulk of raw events -- then use your drill down search to get the right set of stuff. The principle for a correlation search is "gather all your data, tabulate it, and perform a test". You can then pass tokens from your results to the drill down, so that it can be more or less targeted, and easier to read.

question 2, not at this time.

[jcoates_splunk]

Yes, there's always potential to improve... one thing that might help in the meantime is to adjust the level of throttling on correlation searches that produce a lot of hits.

[sspinner]

Thanks. It would be nice to have the option to aggregate results per correlation search in the Incident Review dashboard. Even some of the out-of-box searches, do not aggregate their results, e.g. Excessive Failed Logins