Knowledge Management

Why _time is later than _indextime ??


This data occurs in real time, and I receive it with bundles.

Each source send about 1000~2000 data for average in a day.

I want to compare _indextime and _time(_time is same as the time at the event log's has)

I used query like this.

index=idx_A source="B.D2180323.F0015358*"
| eval indextime=_indextime
| stats values(source) by indextime _time
| eval time_gap=indextime - _time, indextime=strftime(indextime, "%y/%m/%d %H:%M:%S")

I guessed the indextime will be always later than _time, because all events will indexing after the events get over.

Most of results are came out as I gussed, but some events was wiered.

indextime              _time         Time_gap
2018-03-22 1:05 2018-03-22 23:19    -1334
2018-03-22 1:05 2018-03-22 23:25    -1340
2018-03-22 1:05 2018-03-22 23:34    -1349
2018-03-22 1:05 2018-03-22 23:56    -1371

Why some indextime is later than _time?

Tags (2)
0 Karma


try to see the latency,

 * | eval time=_time | eval itime=_indextime | eval latency=(itime  - time) | stats count, avg(latency), min(latency), max(latency) by source

Negative latencies, if observed, usually indicate a system clock difference between the source server (log-source) and the Splunk-server(indexer).

This figure will of course be inaccurate when Splunk indexes historic logs.- just to let you know

0 Karma
Get Updates on the Splunk Community!

Enterprise Security Content Update (ESCU) | New Releases

In the last month, the Splunk Threat Research Team (STRT) has had 2 releases of new security content via the ...

Announcing the 1st Round Champion’s Tribute Winners of the Great Resilience Quest

We are happy to announce the 20 lucky questers who are selected to be the first round of Champion's Tribute ...

We’ve Got Education Validation!

Are you feeling it? All the career-boosting benefits of up-skilling with Splunk? It’s not just a feeling, it's ...