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

Get Updates on the Splunk Community!

Splunk Observability for AI

Don’t miss out on an exciting Tech Talk on Splunk Observability for AI! Discover how Splunk’s agentic AI ...

[Puzzles] Solve, Learn, Repeat: Dereferencing XML to Fixed-length events

This challenge was first posted on Slack #puzzles channelFor a previous puzzle, I needed a set of fixed-length ...

Stay Connected: Your Guide to December Tech Talks, Office Hours, and Webinars!

What are Community Office Hours? Community Office Hours is an interactive 60-minute Zoom series where ...