Getting Data In

Timestamp error: “Failed to parse timestamp. Defaulting to file modtime.

s1j1yem1x
Path Finder

I want to monitor WindowsUpdate.log on windows PC, after selecting the data source, I got a flagged message saying “Failed to parse timestamp. Defaulting to file modtime. How can I resolve this error? Thank you.

0 Karma

richgalloway
SplunkTrust
SplunkTrust

Either your data does not contain timestamps or the timestamps are in an unexpected location/format. If the former, you'll have to live with the message; if the latter, correct the TIME_PREFIX, TIME_FORMAT, and MAX_TIMESTAMP_LOOKAHEAD settings in your props.conf file.

---
If this reply helps you, Karma would be appreciated.
0 Karma

s1j1yem1x
Path Finder

@richgalloway, thanks for your response. I see about 6 props.conf... which one am I supposed to modify and what exactly am I supposed to correct the TIME_PREFIX, TIME_FORMAT, and MAX_TIMESTAMP_LOOKAHEAD settings to?

I'm a newbie learning splunk. Thank you.

Thank you.

alt text

0 Karma

richgalloway
SplunkTrust
SplunkTrust

None of those. Choose Splunk\etc\system\local. Even better is Splunk\etc\apps\<myapp>\local (create it if it doesn't exist). Create a stanza that matches the sourcetype of your data. The exact value of the settings depends on your data. Please share a sample.

---
If this reply helps you, Karma would be appreciated.
0 Karma
Get Updates on the Splunk Community!

Aligning Observability Costs with Business Value: Practical Strategies

 Join us for an engaging Tech Talk on Aligning Observability Costs with Business Value: Practical ...

Mastering Data Pipelines: Unlocking Value with Splunk

 In today's AI-driven world, organizations must balance the challenges of managing the explosion of data with ...

Splunk Up Your Game: Why It's Time to Embrace Python 3.9+ and OpenSSL 3.0

Did you know that for Splunk Enterprise 9.4, Python 3.9 is the default interpreter? This shift is not just a ...