Getting Data In

Timestamp is not recognized

zhou51
New Member

alt text

Use splunk enterprise version 7.2.3,Use the field to extract the timestamp, the time closer to the present can be identified, and the historical time cannot be identified, how to solve

help!help

Tags (1)
0 Karma

to4kawa
Ultra Champion

what's INDEXED_EXTRACTION in props.conf ?

and you should fix indexes.conf

https://docs.splunk.com/Documentation/Splunk/latest/Admin/Indexesconf

frozenTimePeriodInSecs = < nonnegative integer>
* The number of seconds after which indexed data rolls to frozen.
* If you do not specify a 'coldToFrozenScript', data is deleted when rolled to frozen.
* NOTE: Every event in a bucket must be older than frozenTimePeriodInSecs seconds before the bucket rolls to frozen.
* The highest legal value is 4294967295.
* Default: 188697600 (6 years)

reference: https://conf.splunk.com/files/2017/slides/splunk-data-life-cycle-determining-when-and-where-to-roll-...

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Note: This post outlines a proposed architecture and serves as an interest check. If we secure commitments ...