Knowledge Management

Correcting timestamp with ingest-time eval?

PickleRick
SplunkTrust
SplunkTrust

I have a quite unusual case. One of my sources emits logs with a very stupid timestamp format. It consists of a date and time glued together, which on its own is quite ok, but followed with a timezone info in form of time difference vs UTC expressed... in minutes.

So it's not your typical "+0200". No. It's "+120". There's no such timezone format in your strptime format specification so I have to do it some other way. Since _time is crucial to the proper event processing, of course I have to adjust it in ingest time.

I thought about parsing the offset from the timestamp as an independent field and then correcting the _time field before indexing the event. Does it make sense? I don't see any other way of producing correct timestamp from such data.

Labels (1)
0 Karma

isoutamo
SplunkTrust
SplunkTrust
Hi
That should work. If I recall right there are somewhere this kind of examples for using ingest time eval.
R. Ismo

PickleRick
SplunkTrust
SplunkTrust

Thx for confirmation. 🙂

0 Karma

isoutamo
SplunkTrust
SplunkTrust

It was this what I refer https://conf.splunk.com/files/2020/slides/PLA1154C.pdf and 

4. Configuration to Demultiplex Conflicting Time Formats

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!

Vibe-coding, AI, and Splunkcraft: Highlights from the .conf26 Builder Bar

If you stopped by the Builder Bar at .conf26, thank you! This year, we brought ...

Thanks for the Memories: .conf26 Took Learning to New Heights

Thank you, Splunk Community, for making .conf26 in Denver one for the books. From packed Splunk University ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...