Getting Data In

Timestamp in props.conf

splunkingsplun1
Explorer

My event looks like this:

Jan 30 10:32:43 192.168.1.1 Netdefender: 30-01-2014 02:54:05 WARNING

We would like to use the second timestamp for our events. We have configured props.conf in /local like this:

[netdefender]
TIME_PREFIX = \w+\s\d+\s\d{2}:\d{2}:\d{2}\s\d+\.\d+\.\d+\.\d+\s\w+\:\s
MAX_TIMESTAMP_LOOKAHEAD = 44

We are still seeing index time as the timestamp. What are we missing?

Tags (2)
0 Karma
1 Solution

kristian_kolb
Ultra Champion

The config below should work.

[netdefender]
TIME_PREFIX = :\s
TIME_FORMAT = %d-%m-%Y %H:%M:%S

Further things to check:

You have edited the correct props.conf file?

The sourcetype name is correct?

You are aware that this only affects new events coming in?

You have restarted Splunk?

/K

View solution in original post

0 Karma

kristian_kolb
Ultra Champion

The config below should work.

[netdefender]
TIME_PREFIX = :\s
TIME_FORMAT = %d-%m-%Y %H:%M:%S

Further things to check:

You have edited the correct props.conf file?

The sourcetype name is correct?

You are aware that this only affects new events coming in?

You have restarted Splunk?

/K

0 Karma

splunkingsplun1
Explorer

Thank you that did what we needed!

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!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...

Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...

After a whole week of being on call, you fell asleep on your keyboard, and you hit a sequence of buttons that ...