Reporting

BUG: scheduled search fails to load if the search begins with a "pipe" command (6.0.5)

the_wolverine
Champion

The scheduled search is scheduled properly and runs with no errors per _internal log. However the search artifacts are never retrievable. Through a few months of working with support and several troubleshooting binaries, we have discovered that this is caused by some bug with Splunk failing to properly run scheduled search queries that begin with a pipe.

E.g.:
| inputlookup
| tstats

Currently awaiting response and a fix from Splunk. Not sure if other versions are affected.

0 Karma
1 Solution

the_wolverine
Champion

Fixed in version 6.2.7 and 6.3.*

View solution in original post

the_wolverine
Champion

Fixed in version 6.2.7 and 6.3.*

Get Updates on the Splunk Community!

Splunk Enterprise Security 8.0.2 Availability: On cloud and On-premise!

A few months ago, we released Splunk Enterprise Security 8.0 for our cloud customers. Today, we are excited to ...

Logs to Metrics

Logs and Metrics Logs are generally unstructured text or structured events emitted by applications and written ...

Developer Spotlight with Paul Stout

Welcome to our very first developer spotlight release series where we'll feature some awesome Splunk ...