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!

CX Day is Coming!

Customer Experience (CX) Day is on October 7th!! We're so excited to bring back another day full of wonderful ...

Strengthen Your Future: A Look Back at Splunk 10 Innovations and .conf25 Highlights!

The Big One: Splunk 10 is Here!  The moment many of you have been waiting for has arrived! We are thrilled to ...

Now Offering the AI Assistant Usage Dashboard in Cloud Monitoring Console

Today, we’re excited to announce the release of a brand new AI assistant usage dashboard in Cloud Monitoring ...