Splunk Search

First instance of timestamp

mirsmehdi
New Member

Trying to get the first occurrence of the timestamp to be used for _time

LogFile:
2016/05/27 06:30; 2016/05/27 06:29:18 Test1 :Service1
2016/05/27 05:30; 2016/05/27 05:24:16 Test2 :Service2

Have used props.conf to use MAX_TIMESTAMP_LOOKAHEAD=15, and also TIME_PREFIX = ^; still looks at the second timestamp

inputs.conf:

[monitor:LogFile]
index = test_index
sourcetype = sourcetype_new
source = host1

props.conf

[sourcetype_new]
TIME_PREFIX = ^
MAX_TIMESTAMP_LOOKAHEAD = 15

search:

source=host1 sourcetype=sourcetype_new *

Output:

Time                                -  Event
2016/05/27 06:29:18       - 2016/05/27 06:30; 2016/05/27 06:29:18 Test1 :Service1
2016/05/27 05:24:16       - 2016/05/27 05:30; 2016/05/27 05:24:16 Test2 :Service2
Tags (1)
0 Karma

ryanoconnor
Builder

Also keep in mind 2016/05/27 06:30 is 16 characters, so you might want to change your max_timestamp_lookahead to 16.

0 Karma

richgalloway
SplunkTrust
SplunkTrust

Try adding TIME_FORMAT = %Y/%m/%d %H:%M to your sourcetype_new stanza.

---
If this reply helps you, Karma would be appreciated.
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!

Event Series: Telemetry Pipeline Management

Balancing Scale and Spend: Gaining Control Over High-Volume Metrics in Splunk Observability Cloud As ...

Kick the Tires Before You Commit: A Hands-On Tour of the Splunk Observability Cloud ...

Evaluating an enterprise observability platform usually goes like this: fill out a form, get a free trial with ...

Deep insights, no barriers: Splunk Observability Cloud Free Edition

As software delivery cycles continue to accelerate, observability shouldn’t be a luxury — it should be a ...