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!

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 ...

Adoption of RUM and APM at Splunk

    Unleash the power of Splunk Observability   Watch Now In this can't miss Tech Talk! The Splunk Growth ...