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!

What’s new on Splunk Lantern in August

This month’s Splunk Lantern update gives you the low-down on all of the articles we’ve published over the past ...

Welcome to the Future of Data Search & Exploration

You have more data coming at you than ever before. Over the next five years, the total amount of digital data ...

This Week's Community Digest - Splunk Community Happenings [8.3.22]

Get the latest news and updates from the Splunk Community here! News From Splunk Answers ✍️ Splunk Answers is ...