Splunk Search

I am running an import script for an interval of 5 mins to collect data from all sourcetypes and put it into a summary index.

Gunjan92
Engager

I have a situation where in the span of 10 mins there could be a possibility that we didn't get any data from one of the sourcetype for one interval but started getting data for next interval, by this way I am loosing data in summary index. Any suggestion would be helpful.

Here's a part of my query:
| metadata type=sources index=abc
| search source=random
| eval earliest=lastTime - 300
| eval latest=now()
| fields earliest latest

So this random source is collecting data from all the sourcetypes.

Tags (1)

woodcock
Esteemed Legend

This is the reason that most searches of this type run at least 5 minutes back in time, preferably an hour or more. There really is no way around it. You can examine your latency with a search like this:

|tstats max(_indextime) AS indextime WHERE index=_* OR index=* BY index sourcetype _time
| stats avg(eval(indextime - _time)) AS latency BY index sourcetype
| fieldformat latency = tostring(latency, "duration")
| sort 0 - latency
0 Karma

anmolpatel
Builder

Don't really understand the question. Can you please elaborate or provide an example?

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!

Can’t Make It to Boston? Stream .conf25 and Learn with Haya Husain

Boston may be buzzing this September with Splunk University and .conf25, but you don’t have to pack a bag to ...

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