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
Get Updates on the Splunk Community!

What the End of Support for Splunk Add-on Builder Means for You

Hello Splunk Community! We want to share an important update regarding the future of the Splunk Add-on Builder ...

Solve, Learn, Repeat: New Puzzle Channel Now Live

Welcome to the Splunk Puzzle PlaygroundIf you are anything like me, you love to solve problems, and what ...

Building Reliable Asset and Identity Frameworks in Splunk ES

 Accurate asset and identity resolution is the backbone of security operations. Without it, alerts are ...