Splunk Search

Question regarding summary index with saved search

chinmayc469
Explorer

Hello,

I have created a saved search to populate summary index. I am running saved search for every 5 minutes.

What i want is, first time when the saved search runs, it should run with time range as all time.
And from the second time on wards, saved search should with time range as "last 5 mins" (ie, latest=now and earliest=last time when ss ran succesfully)

So that i will avoid duplicate of data in summary index.

How to achieve this?

Thanks in advance.

Tags (1)
0 Karma

skoelpin
SplunkTrust
SplunkTrust

Yep, run the first saved search manually then schedule it thereafter

0 Karma

chinmayc469
Explorer

how about in production machines? we will not have access to change once it is gone to production.

0 Karma

skoelpin
SplunkTrust
SplunkTrust

I don't get what you're asking.. On your production servers, you should backfill against all-time then once your backfilled, you should set up a scheduled search which will populate your summary index going forward. I would also suggest using the python script to backfill. This gives you the ability to ignore data thats already been backfilled and you can run parallel backfills without duplicates

https://docs.splunk.com/Documentation/Splunk/7.1.2/Knowledge/Managesummaryindexgapsandoverlaps

0 Karma

pradeepkumarg
Influencer

The first all time search, you can probably run manually, there after, you should chose earliest and latest with little bit of padding. latest=now is not a good practice as you are not accounting for the delay in the raw data. You can do something like earliest=-8m@m latest=-3m@m so that you account for 180 seconds of delay depending on how busy your indexers and forwarders are.

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

Thanks for the Memories! Splunk University, .conf25, and our Community

Thank you to everyone in the Splunk Community who joined us for .conf25, which kicked off with our iconic ...

Data Persistence in the OpenTelemetry Collector

This blog post is part of an ongoing series on OpenTelemetry. What happens if the OpenTelemetry collector ...

Introducing Splunk 10.0: Smarter, Faster, and More Powerful Than Ever

Now On Demand Whether you're managing complex deployments or looking to future-proof your data ...