Reporting

saved search with collect command not running/not collecting data

kochera
Communicator

Hi,

I've a scheduled saved search running every day to collect events and writting the events to a new index. Running the search interactively is working fine but running the job started by the scheduler is not working at all. No data is written to the new index. Find below the search:

index=access sourcetype="legacy"  [search (index=access sourcetype="tap") OR (index=access sourcetype=vdi) |fields + user ] |collect index=access sourcetype=legacy_spec

Any ideas what might cause this behaviour?

cheers,
Andy

0 Karma
1 Solution

mzorzi
Splunk Employee
Splunk Employee

the output of collect command must be a separate summary index, it can not be the same index :

http://docs.splunk.com/Documentation/Splunk/6.3.1/SearchReference/Collect

View solution in original post

0 Karma

mzorzi
Splunk Employee
Splunk Employee

the output of collect command must be a separate summary index, it can not be the same index :

http://docs.splunk.com/Documentation/Splunk/6.3.1/SearchReference/Collect

0 Karma

kochera
Communicator

Hi,
thanks for your answer. But why is it writting the data properly when running it manually?

cheers,
Andy

0 Karma

woodcock
Esteemed Legend

I would open a support case and ask that exact question.

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Splunk Lantern’s Guide to The Most Popular .conf25 Sessions

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Unlock What’s Next: The Splunk Cloud Platform at .conf25

In just a few days, Boston will be buzzing as the Splunk team and thousands of community members come together ...

Index This | How many sevens are there between 1 and 100?

August 2025 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with this ...