Getting Data In

epoch time stamps not being indexed

smudge797
Path Finder

Im having trouble ingesting these logs with the following format:

{"order":{"custom..........ntType":1,"timestamp":1400083389834}

i.e.
START:
{"order":{
END:
"timestamp":}

Splunk is having issues with the content of the event and the time stamp. Any help much appreciated!

0 Karma

somesoni2
Revered Legend

Try these in your props.conf

[Yoursourcetype]
BREAK_ONLY_BEFORE=\{\"order\"
NO_BINARY_CHECK=1
SHOULD_LINEMERGE=true
TIME_PREFIX=\"timestamp\":

somesoni2
Revered Legend

MAX_TIMESTAMP_LOOKAHEAD is property to indicate how long the timestamp field/value can be. E.g. in your example its 13 (no of digits in epoch time). If there are milliseconds there could be decimal point and 3 more digits. So it would be good idea to set this property to avoid capturing extra values. But since your timestamp is the last field in your event, it may not be necessary.

smudge797
Path Finder

There can be around 3000 characters in each event and each time stamp is at the end?

0 Karma

richgalloway
SplunkTrust
SplunkTrust

Depending on the size of your log entries, you may also want to add MAX_TIMESTAMP_LOOKAHEAD to your props.conf file.

---
If this reply helps you, Karma would be appreciated.
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!

(re)Introducing the Splunk Community Champions + 2026 – 2027 Splunk MVPs ...

This program exists as a channel to empower and recognize Splunk advocates and help supercharge initiatives to ...

Introducing the 2026 - 2027 SplunkTrust cohort!

The goal of the SplunkTrust™ membership has historically been to acknowledge and recognize those who go above ...

Pro Tips for .conf26: How to Prep Like a Splunk Veteran

There’s no shortage of incredible content lined up for .conf26 in Denver, from deep-dive technical sessions ...