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!

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...

New in Observability Cloud - Explicit Bucket Histograms

Splunk introduces native support for histograms as a metric data type within Observability Cloud with Explicit ...