Splunk Search

How can i efficiently discard the event stream of a search?

jrodman
Splunk Employee
Splunk Employee

Suppose I have a search such as

sourcetype=apache errors

which finds errors that I care about. Now, suppose I want to send these errors, on certain conditions, so I want to use the alert_condition feature of savedsearches.conf. Let's say the condition I want to use is that it is not working hours -- totally unrelated to the original search. However, alert_condition is fed the event stream from the original search.

How can I efficiently dump the original stream, when needed?

The best I can come up with is

alert_condition = head 1 | where 1=2 | append [search ....]

Can this be done more neatly?

Tags (3)
1 Solution

jrodman
Splunk Employee
Splunk Employee

Apparently the 'best I could come up with' is the best we have.

That should be efficient, it's just a little ugly to read.

View solution in original post

jrodman
Splunk Employee
Splunk Employee

Apparently the 'best I could come up with' is the best we have.

That should be efficient, it's just a little ugly to read.

Get Updates on the Splunk Community!

Routing logs with Splunk OTel Collector for Kubernetes

The Splunk Distribution of the OpenTelemetry (OTel) Collector is a product that provides a way to ingest ...

Welcome to the Splunk Community!

(view in My Videos) We're so glad you're here! The Splunk Community is place to connect, learn, give back, and ...

Tech Talk | Elevating Digital Service Excellence: The Synergy of Splunk RUM & APM

Elevating Digital Service Excellence: The Synergy of Real User Monitoring and Application Performance ...